Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-12043

Allow certain push events to not trigger a webhook from Bitbucket Server



    • Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • None
    • Webhooks
    • None
    • 8
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      Request from Sake Paulusma on https://community.atlassian.com/t5/Bitbucket-articles/Atlassian-supported-Jenkins-integration-for-Bitbucket-Server

      In Webhook to Jenkins for Bitbucket is it possible to define users from which commits should be ignored (the version we use (the free one), this is bugged).

      In our current environment Jenkins gets a push request to preform some actions and starts a job. One of those actions in this job is to trigger the Maven release plugin. Maven creates a new version and afterwards does a commit to Bitbucket where all pom.xml files are edited with the increased (snapshot) version. But because there's a new commit, Bitbucket sends push request to Jenkins and job starts again and gets in a infinite loop.

      They have a workaround, but it's a nasty one; abort the Jenkins job if commit is from Jenkins (the commit above). This results in a failed job, sends the information that a job failed and someone needs to check why it failed. Another annoyance are the red bars and more failed jobs which results in polluted reports.

      Possible solutions:

      • Do not trigger a push webhook if push is done by a specific user
      • Exisiting of specific keyword in commit message doesn't trigger a push webhook




            Unassigned Unassigned
            ikhan Imran Khan
            4 Vote for this issue
            6 Start watching this issue