Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18527

Don't trigger jobs which don't have SCM changes

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Postponed
    • Icon: Major Major
    • multijob-plugin
    • None
    • Jenkins v1.520

      Hi there,

      This plugin looks perfect for what I need accept one thing - I don't want the downstream phases/jobs to trigger if they don't have any scm changes. My setup is as follows:

      MainJob
    Phase 1
        JobA
        JobB 
    Phase 2
        JobC

      MainJob has a Perforce view that sees my entire depot.
      JobA, JobB and JobC have Perforce views that are tailored to the specific job.

      So, if a file is changed that is only in JobA's view (it'll be in the MainJob view too because that sees everything) then I expect MainJob and JobA to build but I see MainJob, JobA, JobB and JobC building.

      I thought the "Exposed SCM" flag might fix this issue but when I enabled it the behaviour was the same.

      Can you add support for this requirement? Or am I misunderstanding something?

          [JENKINS-18527] Don't trigger jobs which don't have SCM changes

          Yoram Michaeli added a comment -

          Closing issue as part of tikal-multijob-plugin issues cleanup. If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)

          Yoram Michaeli added a comment - Closing issue as part of tikal-multijob-plugin issues cleanup. If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues  (you can refer to this issue in its description)

            Unassigned Unassigned
            tfields Thomas Fields
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: