Start a build definition when another one finish
Hi,
I have this situation. In the project that I work for, we have in RTC one build definition and build engine correctly configured and working fine to generate daily new builds. The output of it is a .zip file with the compiled product ready to be installed. But I have no control on this since it uses a centralized and complex build server for multiple projects with high security restrictions. What I want to do is to create another build definition and build engine to execute the deployment/install of the product and trigger automated tests in the product after the first build is finished. I will have total control on this second build definition and build engine. I would like to have some suggestions on how I could do that. Is there a way to configure the successful end of the first build as an event that will start the execution of the second one? I appreciate any suggestions. |
3 answers
The Ant tasks are included in the Build System Toolkit, in the buildtoolkit directory (a sibling to the buildengine directory, where JBE is located). For an Ant build definition, JBE launches Ant as a separate process, and by default it includes the buildtoolkit jars on the class path. This is configurable in the build definition.
For details, see https://jazz.net/wiki/bin/view/Main/BuildFAQ#What_is_in_the_Build_System_Tool |
|
Hi Edgar,
I think this ant tasks approach may help. I'll spend some time testing it. I'm not sure if I'll have the right permissions to add it to be executed in the initial build definition but for sure it worth to try. I have another question. This ant tasks are available at any build engine or is it necessary to do some specific configuration? Thanks a lot. |
|
Hi Leandro,
You can use the requestTeamBuild Ant task to request a build for another build definition (to do the deployment). Like any other manually requested or scheduled build, the first supporting build engine that's available will pick up the request. The task also allows you to override the values of build properties, if needed. One thing you can do is to pass on the requesting build's buildResultUUID as a new build property, then use this in the script for the deployment build to create links between the builds, using the linkPublisher Ant task. For more on the Ant tasks, see the Ant task reference section in the Help. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.