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

Jenkins Multibranch Pipeline Scan infinite re-build


    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • - Linux Mint 18.3 (Ubuntu 16.04)
      - Jenkins 1.4.2 Core 2.107.1
      - Git 2.7.4
      - Docker 18.03.0-ce
      - Maven 3
      - JDK 1.8

      Hi, I would post here a question already asked onhttps://stackoverflow.com/questions/49736540/jenkins-multibranch-pipeline-scan-infinite-re-build.
      I have to deal with the following scenario:

      1. I am running my Jenkins Pipeline on Blue Ocean + Git (+ Maven).
      2. I have setup the "Scan Multibranch Pipeline" option to check every X minutes if something has changed on the Git repo, and in that case start the job again...
      3. My pipeline implements the usual build and test stages.
      4. My pipeline, as last stage, increments the snapshot version and pushes the updated POM to Git.

      Step 4 triggers my issue: the "Scan Multibranch Pipeline" feature gets (forever) the branch as updated (by the commit at step 4).

      How could I update the last "Scan Multibranch Pipeline" commit hash reference in order to stop job re-triggering?

      Thank you very much!

            Unassigned Unassigned
            antonio_petricca Antonio Petricca
            0 Vote for this issue
            2 Start watching this issue