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

Parameterized build always triggered even w/o SCM changes

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

        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

          Activity

          Hide
          markewaite Mark Waite added a comment -

          This seems very similar to an earlier bug report that wanted git polling to use the default value of the parameterized branch name from a Freestyle job.

          Is that also what you're expecting?

          Show
          markewaite Mark Waite added a comment - This seems very similar to an earlier bug report that wanted git polling to use the default value of the parameterized branch name from a Freestyle job. Is that also what you're expecting?
          Hide
          marsze Marian Szewczyk added a comment - - edited

          If I understand you correctly, it seems like this is what I want to achieve. I could not find a similar bug report. The expected behavior should not be any different from the un-parameterized job: Git polling should use "**" as branch specifier (except that it comes from the parameter's default value) and the build should be triggered on new changes only. Except that I can specify a specific branch name whenever I decide to run the job manually.

          Show
          marsze Marian Szewczyk added a comment - - edited If I understand you correctly, it seems like this is what I want to achieve. I could not find a similar bug report. The expected behavior should not be any different from the un-parameterized job: Git polling should use "**" as branch specifier (except that it comes from the parameter's default value) and the build should be triggered on new changes only. Except that I can specify a specific branch name whenever I decide to run the job manually.

            People

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

              Dates

              • Created:
                Updated: