Triggering of builds gone wild
We recently upgraded to 2017.2.3 fro 7.0.3. We where able to get everything upgraded and it seemed like every thing was working.
On the weekend we have some jobs that are triggered at certain times to perform patching and chef runs in some linux environments. the Time trigger, triggers patching and the chef run fires up on a finished patching build trigger. Once patching and chef are done we then have a finished build trigger on some deploys (looking at the chef build task completion as a finished build trigger.)
Today I noticed that we have a bunch of build jobs that where triggered and I would go the the queues and delete all the jobs only to see them come back into the Queue over and over again until I deleted the triggers or disabled them.
Is there something that would cause this? These where working fine in the 7.0.3 version and only started to do this once we upgraded.
Any guidance or direction would be appreciated.
Please sign in to leave a comment.
Hi Lance,
it's hard to point out from that description. This scenario shouldn't really happen but using the Finish build trigger might behave slightly differently than just using snapshot dependencies. Is there any reason to have the finish build trigger instead of just the snapshot dependency with the triggers at the end of the chain? It would be useful to have screenshots of all the triggers and dependency set ups.