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

Button to add new branches not showing in pipeline SCM configuration

      Steps to reproduce

      Create a pipeline

      Try to get the Jenkinsfile from SCM using the Bitbucket integration plugin.

      When you try to add new branches you see that the button is missing. The button is showing up when you select Git as SCM.

       

      Workaround:

      By adding commas you can chain multiple branch selectors together in a single field.

       

          [JENKINS-69203] Button to add new branches not showing in pipeline SCM configuration

          Manuel Cárdenas-Blanco added a comment - - edited

          I have unassigned this ticket from markwaite as I think that even if it is related to the git plugin,  the problem seems to be on the Bitbucket side. Please feel free to reassign the issue back if you think otherwise.

          Manuel Cárdenas-Blanco added a comment - - edited I have unassigned this ticket from markwaite as I think that even if it is related to the git plugin,  the problem seems to be on the Bitbucket side. Please feel free to reassign the issue back if you think otherwise.

          Hi Manuel, thanks for the report. Yes this is a Bitbucket issue, not a git one.

          I ran a quick test with a pipeline job, creating an SCM, and noticed the button was not missing. Can you please share some logging and a screenshot of your configuration screen so we can see if an error underlies this?

          Martin Henschke added a comment - Hi Manuel, thanks for the report. Yes this is a Bitbucket issue, not a git one. I ran a quick test with a pipeline job, creating an SCM, and noticed the button was not missing. Can you please share some logging and a screenshot of your configuration screen so we can see if an error underlies this?

          We have seen that multiple branches can be added as comma-separated elements. But it is confusing as the behavior differs from the one observed if you select Git as SCM. In fact, if you delete the branch selection section, you cannot add it again. The button does not show at the bottom of the branches specifier.

           

          • Jenkins 2.346.x
          • Bitbucket server plugin 3.0.0
          • Git plugin 4.11.3

          Bitbucket server plugin includes a dependency on an older version of the Git plugin, and the button position has changed in the Git plugin more recent versions. Maybe this is a red herring but we considered it worth mentioning it here.

          Manuel Cárdenas-Blanco added a comment - We have seen that multiple branches can be added as comma-separated elements. But it is confusing as the behavior differs from the one observed if you select Git as SCM. In fact, if you delete the branch selection section, you cannot add it again. The button does not show at the bottom of the branches specifier.   Jenkins 2.346.x Bitbucket server plugin 3.0.0 Git plugin 4.11.3 Bitbucket server plugin includes a dependency on an older version of the Git plugin, and the button position has changed in the Git plugin more recent versions. Maybe this is a red herring but we considered it worth mentioning it here.

          Thanks for the response here. Interestingly the button appears on Jenkins 2.346.x and plugin version 3.0.0 using the bundled git plugin version, but bumping to (in my case 4.11.4), the button disappears. Frustratingly there's no logging, but this looks to be due to a versioning issue.

          Can you verify that using comma-separated branch selectors are a viable workaround for your use case until this bug can be resolved?

          Martin Henschke added a comment - Thanks for the response here. Interestingly the button appears on Jenkins 2.346.x and plugin version 3.0.0 using the bundled git plugin version, but bumping to (in my case 4.11.4), the button disappears. Frustratingly there's no logging, but this looks to be due to a versioning issue. Can you verify that using comma-separated branch selectors are a viable workaround for your use case until this bug can be resolved?

          mhenschke_atlassian thank you for your update. We have validated the workaround successfully. We will wait for the fix to improve user experience though as it is a little bit confusing, specially when you compare the observed behavior with the one offered by Git plugin.

          Manuel Cárdenas-Blanco added a comment - mhenschke_atlassian thank you for your update. We have validated the workaround successfully. We will wait for the fix to improve user experience though as it is a little bit confusing, specially when you compare the observed behavior with the one offered by Git plugin.

          Lowering the priority as there is a workaround to this issue.

          Martin Henschke added a comment - Lowering the priority as there is a workaround to this issue.

            Unassigned Unassigned
            javidad Manuel Cárdenas-Blanco
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: