I'm migrating a lot of fairly hairy infrastructure around to use jerkins-workflow.
At the moment, we have a number of projects that use triggering: - proj-build proj-ITU proj-robot-tests What I want to migrate is - proj-build builds every commit. proj-ITU is very expensive, so it gets triggered on successful proj-build builds; but - it only builds against *master*, so multiple triggerings will just queue it to build once. I'm not sure the best way to model that in workflow (or even if that's the best option). Something like a stage that says 1) "if there is an 'ITU' stage currently building, wait until it finishes. 2) If there is another build, where the build number is later than us, and that build started the ITU stage (or is, like us, waiting to enter that stage) then exit. (I.E: no point in running integration tests against a version that's now stale). Is that something do-able in workflow? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPYP83RtRLXwCSV8ZqbpoA_cBg4OSzV-G30s9RhMgYqaoP_Y5Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
