On Wed, Dec 19, 2018 at 2:51 PM <[email protected]> wrote: > it is necesary build subprojects in a ordered sequence, but only when it is > necessary, and in a predectible schedule, not when SCM changes are detected.
But this is just what `SCMTrigger` does, if you give it a polling schedule (and do not register webhooks). Maybe I am missing something. Anyway if you want slightly customized behavior, perhaps you just want to write a new `Trigger` implementation. > in a future in Pipeline Jobs Note that in Pipeline you can also inspect `currentBuild.changeSets` in your script and decline to do any real work if it is empty (just `return` early). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/CANfRfr0M_VK%2B%3DeWQXuyuqtyKD0_qCA9FYjb4bANcQLRAF0EYTg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
