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

Multibranch pipeline fails due to neglected non-default port during SCM checkout

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • None

      Reproduction steps

      1. install jenkins and that plugin (my case: as docker container)
      2. configure jenkins to configure Bitbucket Server integration with non-default port
        1.1 e.g. https://your.bitbucketserver.com:9443/
      3. setup multibranch pipeline
        2.1 using Bitbucket server as your branch sources
        2.2 select your configured server integration and working credentials
        2.3 see success of that connection by finding and selecting the project name and the repo-name
        2.4 save your changes
      4. trigger build pipeline
      5. observe a branch SCM checkout

      Expected Results

      successful branch checkouts in step 4
      fetch from same URL as configured in jenkins Bitbucket server integration used for branch detection

      4.1 logs: git config remote.origin.url https://your.bitbucketserver.com:9443/scm/yourproject/yourrepo.git # timeout=10

      Actual Results

      step
      4. observe that each branch SCM checkout times out
      4.1 logs: git config remote.origin.url https://your.bitbucketserver.com/scm/yourproject/yourrepo.git # timeout=10

      see missing sample port :9443 above!

      For non-default git repos (or Bitbucket server) this makes the plugin unusable - for me this is a blocker, classify this according to your policies
      (this also applies to the "sister" plugin Bitbucket Branch Source Plugin)

            Unassigned Unassigned
            orfi Hans
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: