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

Add option to include a prefix to include the name of Bitbucket notification build status

XMLWordPrintable

      There might be more than one Jenkins instance for whatever reason serving the same Bitbucket repository - they might be separate CI and CD servers or CD servers per region or whatever other reason, really.

      Right now build statuses (if jobs were named the same way) clashes so you can only see the last (slowest job) status.

      There should be a new option for the build status trait that allows to include jenkins root URL into commit status.
      There should be a new option for which use can specify a key, a string to indentify the Jenkins job to be included as prefix of the name for build status notification trait.

          [JENKINS-65741] Add option to include a prefix to include the name of Bitbucket notification build status

          Dee Kryvenko created issue -
          Dee Kryvenko made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Dee Kryvenko added a comment -

          PR please https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/454

          Dee Kryvenko added a comment - PR please  https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/454
          Dee Kryvenko made changes -
          Description Original: There might be more than one Jenkins instance for whatever reason serving the same Bitbucket repository - they might be separate CI and CD servers or CD servers per region or whatever other reason, really.

          Right now build statuses (if jobs were named the same way) clashes so you can only see the last (slowest job) status.

          There should be a new trait for Bitbucket Branch Source plugin that allows to include jenkins root URL into commit status text and key.           		New: There might be more than one Jenkins instance for whatever reason serving the same Bitbucket repository - they might be separate CI and CD servers or CD servers per region or whatever other reason, really.

          Right now build statuses (if jobs were named the same way) clashes so you can only see the last (slowest job) status.

          There should be a new option for the build status trait that allows to include jenkins root URL into commit status.
          Dee Kryvenko made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Dee Kryvenko made changes -
          Summary Original: Bitbucket commit status key should include jenkins server URL New: Bitbucket commit status should include jenkins server URL
          Dee Kryvenko made changes -
          Link New: This issue is related to JENKINS-46250 [ JENKINS-46250 ]

          Nikolas Falco added a comment -

          The server URL is too long to be shown in the space dedicated for Bitbucket Cloud. Maybe Jenkins label could be a better solution but does not cover the case the same Jenkins instance have two different project with different name that build the same repository but is using different pipelines, one that build and other one that perform integration tests.

          Nikolas Falco added a comment - The server URL is too long to be shown in the space dedicated for Bitbucket Cloud. Maybe Jenkins label could be a better solution but does not cover the case the same Jenkins instance have two different project with different name that build the same repository but is using different pipelines, one that build and other one that perform integration tests.
          Nikolas Falco made changes -
          Issue Type Original: Task [ 3 ] New: Improvement [ 4 ]
          Nikolas Falco made changes -
          Assignee Original: Dee Kryvenko [ llibicpep ] New: Nikolas Falco [ nfalco ]

            nfalco Nikolas Falco
            llibicpep Dee Kryvenko
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: