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

Bitbucket Pipeline display name should never be calculated

XMLWordPrintable

      Problem
      It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository.

      What you should see
      Ultimately the experience of this plugin should be inline with the Github plugin. The Github plugin does not calculate the display name. If the display name is not set, then it should fall back to the job name.

        1. hellonode bitbucket 2017-01-25 14-03-46.png
          hellonode bitbucket 2017-01-25 14-03-46.png
          28 kB
        2. hellonode Config [Jenkins] 2017-01-25 14-03-21.png
          hellonode Config [Jenkins] 2017-01-25 14-03-21.png
          130 kB

          [JENKINS-41407] Bitbucket Pipeline display name should never be calculated

          Stephen Connolly added a comment -

          Fixed in https://github.com/jenkinsci/bitbucket-branch-source-plugin/commit/a4c6bf39b83168ff62fc622bd4084ef90cf810c0#diff-dbebe1606f4711ed03640cf707dc6c23R969

          Stephen Connolly added a comment - Fixed in https://github.com/jenkinsci/bitbucket-branch-source-plugin/commit/a4c6bf39b83168ff62fc622bd4084ef90cf810c0#diff-dbebe1606f4711ed03640cf707dc6c23R969

          Stephen Connolly added a comment -

          Fix released in 2.2.0

          Stephen Connolly added a comment - Fix released in 2.2.0

          Joerg Schwaerzler added a comment -

          Just upgraded to 2.2.12 as we have more than one multibranch job per repository. Is there any reason why the repository name is used by default for the display name if the display name is not set explicitly?
          This is very annoying as

          • It doesn't follow the approach used for all other jobs (only use the display name if set)
          • We have to configure the display name now for each of those jobs although it should be enough to use the job name as default display name

          Is there a chance to get a fix for that? To be honest reading this ticket I'd say that it isn't fixed (at least not in 2.2.11 / 2.2.12):
          "If the display name is not set, then it should fall back to the job name."

          That is exactly what we would need. Currently the fall back is the repository name not the job name.

          Joerg Schwaerzler added a comment - Just upgraded to 2.2.12 as we have more than one multibranch job per repository. Is there any reason why the repository name is used by default for the display name if the display name is not set explicitly? This is very annoying as It doesn't follow the approach used for all other jobs (only use the display name if set) We have to configure the display name now for each of those jobs although it should be enough to use the job name as default display name Is there a chance to get a fix for that? To be honest reading this ticket I'd say that it isn't fixed (at least not in 2.2.11 / 2.2.12): " If the display name is not set, then it should fall back to the job name. " That is exactly what we would need. Currently the fall back is the repository name not the job name.

            stephenconnolly Stephen Connolly
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: