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

Unable to trigger a build via webhook push - when there is a fast forward commit (no new commit)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • git-plugin
    • None
    • Git Plugin - git:3.12.1
      Jenkins Version - 2.387.1

      Build is not getting triggered via webhook push (/git/notifyCommit)  from gitlab when there is a fast forward commit (i.e., the same SHA is being added to the target branch that was there on source branch). 

      Our requirement is that we are promoting changes from one branch to another and expecting the build to be triggered for every merge. In some scenarios that merge is a fast-forward commit (i.e., same SHA getting pushed to target branch) and in these scenarios the build is not getting triggered.

      As per https://issues.jenkins.io/browse/JENKINS-56156 it seems once a SHA-1 is build then the same SHA-1 is not considered to be build again even though it is a different branch.

      Please help us know if we have option to overcome this limitation.

            Unassigned Unassigned
            nturner Naseer
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: