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

Using a specific global library version in consumers sometimes causes notifications of build success/failure on the library that they consume

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Critical
    • Resolution: Fixed
    • None
    • bitbucket server 4.13.0
      bitbucket branch source 2.0.2
      git plugin 3.0.4

    Description

      It looks like other Bitbucket Branch Source folders that consume a global library in Bitbucket, it also notifies that commit of that repository of failure or success (sometimes?).

      Jenkinsfile

      @Library('myLibrary@0.1.0')
      
      node {
        sh 'exit 1'
      }
      
      

      that is a contrived example, but see the attached image for multiple notifications that don't stem from this repository that seem to come from other consuming organization folder jobs.

      Attachments

        Issue Links

          Activity

            mkobit Mike Kobit added a comment -

            I believe this was fixed by stephenconnolly

            mkobit Mike Kobit added a comment - I believe this was fixed by stephenconnolly
            stephenconnolly Stephen Connolly added a comment - https://github.com/jenkinsci/bitbucket-branch-source-plugin/blame/master/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L103 should have fixed it IIUC

            Believed fixed as a side effect of JENKINS-43507

            stephenconnolly Stephen Connolly added a comment - Believed fixed as a side effect of JENKINS-43507

            Using branch source plugin version 2.11. I still can see this issue - at least it really looks like this issue. Can you confirm that it is still fixed?

            macdrega Joerg Schwaerzler added a comment - Using branch source plugin version 2.11. I still can see this issue - at least it really looks like this issue. Can you confirm that it is still fixed?
            falcon benoit guerin added a comment -

            Using version 2.2.12, I still see this issue too.

            Both my pipeline librairies, configured as global with implicit load, and the repository being built are notified of build status.

            falcon benoit guerin added a comment - Using version 2.2.12, I still see this issue too. Both my pipeline librairies, configured as global with implicit load, and the repository being built are notified of build status.

            People

              amuniz Antonio Muñiz
              mkobit Mike Kobit
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: