Pre-deliver procedure enforced by RTC+Jenkins
Hi all,
I'm interested in enforcing a pre-deliver procedure using RTC and Jenkins:
1. When a developer finishes writing his code and performs check-in, a Jenkins build wakes up automatically to test the code.
2. Deliver is allowed only if all change sets passed build test successfully.
2. Deliver is allowed only if all change sets passed build test successfully.
How can I implement this procedure using RTC and Jenkins?
Thanks!
Yael
Accepted answer
Hi,
There is no out of the box solution for enforcing any pre-deliver steps.
There are some solutions to handle post deliver builds, provided outside the product, like discussed in,
https://jazz.net/forum/questions/132739/jenkins-polling-is-too-slow-can-rtc-notify-jenkins-immediately
https://jazz.net/forum/questions/76612/post-commit-hook-in-rtc?page=1&focusedAnswerId=116585#116585
Thanks,
Sridevi
There is no out of the box solution for enforcing any pre-deliver steps.
There are some solutions to handle post deliver builds, provided outside the product, like discussed in,
https://jazz.net/forum/questions/132739/jenkins-polling-is-too-slow-can-rtc-notify-jenkins-immediately
https://jazz.net/forum/questions/76612/post-commit-hook-in-rtc?page=1&focusedAnswerId=116585#116585
Thanks,
Sridevi
2 other answers
We have no operational behavior on check-in so only deliver can actually do something.
If you can answer the question how the deliver advisor can know that all the changes are builtin Jenkins, you could try something. I have worked with some colleagues looking into what would have to be done to make this feasible and it is very complex and creating it is likely very expensive.
If you can answer the question how the deliver advisor can know that all the changes are builtin Jenkins, you could try something. I have worked with some colleagues looking into what would have to be done to make this feasible and it is very complex and creating it is likely very expensive.