# Best practise for DTAP

**URL:** <https://forum.ansible.com/t/best-practise-for-dtap/18697>\
**Category:** Ansible Project\
**Created:** [July 7, 2015, 6:10am UTC](https://forum.ansible.com/t/best-practise-for-dtap/18697 "2015-07-07T06:10:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marcel\_van\_den\_Brink](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@Marcel\_van\_den\_Brink](https://forum.ansible.com/u/Marcel_van_den_Brink)\
**Post date:** [July 7, 2015, 6:10am UTC](https://forum.ansible.com/t/best-practise-for-dtap/18697/1 "2015-07-07T06:10:32Z")

</div>

Hi,

I was wondering if someone has some best practises regarding a workflow using Git in a DTAP environment.

It is usually the case, that you use a more experimental version of your scripts on development and test. A more stable version should be used in acceptance. Production should be fully stable.

So my question is, how do you handle changes going through DTAP?

Cheers,  
– Marcel

---

<div class="post-metadata">

**Author:** ![Jim\_Gumbley](https://avatars.discourse-cdn.com/v4/letter/j/958977/32.png) [@Jim\_Gumbley](https://forum.ansible.com/u/Jim_Gumbley)\
**Post date:** [July 7, 2015, 4:02pm UTC](https://forum.ansible.com/t/best-practise-for-dtap/18697/2 "2015-07-07T16:02:52Z")

</div>

Perhaps use a deployment pipeline? [http://martinfowler.com/bliki/DeploymentPipeline.html](http://martinfowler.com/bliki/DeploymentPipeline.html)