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

Parameterized build always triggered even w/o SCM changes

XMLWordPrintable

      Initial (working) configuration: The job is configured to be triggered by SCM changes using the Git plugin. Branch specifier is "**" (= any branch). So far, this works as expected. SCM is queried regularly and the build is triggered if new commits are found.

      Then I checked the "build is parameterized" option and added a parameter "BRANCH" with default value "**". This doesn't break things yet. BUT when I now configure this parameter "${BRANCH}" as branch specifier in the check SCM build step, the build is triggered EVERY time, even if there are no new changes.

      The log says the Build was triggered by SCM changes. But it also says that there were no changes.

        1. branch.jpg
          branch.jpg
          5 kB
        2. no_changes.jpg
          no_changes.jpg
          12 kB
        3. parameter.jpg
          parameter.jpg
          11 kB
        4. poll_log.jpg
          poll_log.jpg
          29 kB
        5. trigger.jpg
          trigger.jpg
          11 kB

            Unassigned Unassigned
            marsze Marian Szewczyk
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: