• Type: Bug
• Resolution: Not A Defect
• Priority: Major
• Component/s: workflow-multibranch-plugin
• Labels:

  • git
  • jenkins
  • pipeline
  • scm
• Environment:

  - 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

[JENKINS-50678] Jenkins Multibranch Pipeline Scan infinite re-build

Antonio Petricca created issue - 2018-04-09 15:45

Antonio Petricca made changes - 2018-04-09 15:47

Summary

Original: Jenkins Multibranch Pipeline Scan infinite re-build Ask

New: Jenkins Multibranch Pipeline Scan infinite re-build

Antonio Petricca made changes - 2018-04-09 15:47

Description

Original: Hi, I would post here a question already asked on [Stack Overflow|[https://stackoverflow.com/questions/49736540/jenkins-multibranch-pipeline-scan-infinite-re-build].] 0down vote [favorite|https://stackoverflow.com/questions/49736540/jenkins-multibranch-pipeline-scan-infinite-re-build]   I have to deal with the following scenario:  # I am running my Jenkins Pipeline on Blue Ocean + Git (+ Maven).  # 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...  # My pipeline implements the usual build and test stages.  # 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!

New: Hi, I would post here a question already asked on[https://stackoverflow.com/questions/49736540/jenkins-multibranch-pipeline-scan-infinite-re-build].     I have to deal with the following scenario:  # I am running my Jenkins Pipeline on Blue Ocean + Git (+ Maven).  # 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...  # My pipeline implements the usual build and test stages.  # 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!

Andrew Bayer made changes - 2018-08-08 18:04

Component/s		New: workflow-multibranch-plugin [ 21465 ]
Component/s	Original: pipeline [ 21692 ]

Vivek Pandey made changes - 2018-11-16 16:55

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Resolved [ 5 ]