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

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • None
    • bitbucket server 4.13.0
      bitbucket branch source 2.0.2
      git plugin 3.0.4

      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.

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

              Created:
              Updated:
              Resolved: