Multibranch-Pipeline: Unchanged Jobs should not trigger new builds

[Markus Schwarz]

Hi,

I created a bunch of multibranch-pipeline jobs with jobDSL, works like a charm. The problem is, whenever I change or add a job, all jobs get scheduled builds for every branch, even if the job has not changed at all. With a large number of jobs this is quite annoying as it blocks jenkins slaves for no reason. A workaround would be to create multiple seed jobs which then handle only a few dsl-jobs, but this can't be the right way.

Maybe I'm doing something wrong here, then it would be nice to get some advice how to change the behaviour. If it is intended behaviour, jobDSL is sadly not the way we can follow.

Thanks

Markus

[misha]

I'm having the same issue, adding new job to DSL scheme will trigger all existing jobs and send unnecessary e-mails. Is there a workaround to not trigger existing jobs? I'm think one possible way to disable the trigger is this option from DSL plusing itself:

Action for existing jobs and views:

Ignore changes I will test it myself and see if it solves the problem.

[Daniel Spilker]

This has been fixed in 1.62: https://issues.jenkins-ci.org/browse/JENKINS-43693

Daniel

--
You received this message because you are subscribed to the Google Groups "job-dsl-plugin" group.
To unsubscribe from this group and stop receiving emails from it, send an email to job-dsl-plugin+unsubscribe@googlegroups.com.
To post to this group, send email to job-dsl-plugin@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/job-dsl-plugin/3c0b8dae-bc2a-4f7d-b99d-972f6398ec44%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.