Build deployment for small department
CLM 4.0.5
Hello, we have a group of 10 developers who work in a dev environment, but are tasked with creating and maintaining a QA and Production environment as well. They currently just use Ant tasks to do builds. Since this is not a large ($) company, tools like BuildForge or UC Deploy are not options...
How do current users migrate builds from DEV->QA->Production? Does it always require just manually moving items?
Hello, we have a group of 10 developers who work in a dev environment, but are tasked with creating and maintaining a QA and Production environment as well. They currently just use Ant tasks to do builds. Since this is not a large ($) company, tools like BuildForge or UC Deploy are not options...
How do current users migrate builds from DEV->QA->Production? Does it always require just manually moving items?
Accepted answer
Hi Mahari,
I do not fully understand your requirement about "migrate builds from DEV->QA->Production". Do you mean deliver change set from DEV stream to QA and Production stream after build?
You can have a look the article https://jazz.net/library/article/649 which introduces the "Post-build Deliver" function.
Hope it's helpful.
Comments
Hello, delivering to streams seem like an out-of-the-box thing. I am referring to machines.... I built the application, now i want to put that build in a QA environment. After it is tested, I want to put that in to production.
Again, no finances for something like UDeploy.
If you don't have a deploy tool like uDeploy, you may consider to write your own deployment script and add in the post build step in the build definition.