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

Bitbucket Server Integration clones from upstream instead of mirror for newly created jobs in 3.2+

XMLWordPrintable

    • 3.2.2

      Bitbucket Server Integration plugin has a regression in 3.2 where it clones from the upstream server, even when configured to clone from the mirror for newly created jobs. Jobs created prior to 3.2 will continue to clone from the mirror.

      Steps to reproduce:

      1. Upgrade Bitbucket Server Integration to 3.2
      2. Create a job that is configured to clone from a mirror
      3. Build the job

      Expected output

      • Job clones from the mirror

      Actual output

      • If you inspect the console log, you will see that the job actually clones from the usptream.

      Workaround

      This is not reproducible in 3.1.0.
      No known workaround.

          [JENKINS-68634] Bitbucket Server Integration clones from upstream instead of mirror for newly created jobs in 3.2+

          Kristy Hughes created issue -
          Kristy Hughes made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]
          Kristy Hughes made changes -
          Description Original: Bitbucket Server Integration plugin has a regression in 3.2.2 where it clones from the upstream server, even when configured to clone from the mirror. This is not reproducible in 3.1.0. New: Bitbucket Server Integration plugin has a regression in 3.2.2 where it clones from the upstream server, even when configured to clone from the mirror.

          This is not reproducible in 3.1.0.
          No known workaround.
          Kristy Hughes made changes -
          Description Original: Bitbucket Server Integration plugin has a regression in 3.2.2 where it clones from the upstream server, even when configured to clone from the mirror.

          This is not reproducible in 3.1.0.
          No known workaround.           		New: Bitbucket Server Integration plugin has a regression in 3.2.2 where it clones from the upstream server, even when configured to clone from the mirror.

          h3. Steps to reproduce:

          1. Create a job that is configured to clone from a mirror
          2. Build the job

          h3. Expected output

          * Job clones from the mirror

          h3. Actual output

          * If you inspect the console log, you will see that the job actually clones from the usptream.

          h4. Workaround

          This is not reproducible in 3.1.0.
          No known workaround.
          Kristy Hughes made changes -
          Summary Original: Bitbucket Server Integration clones from upstream instead of mirror in 3.2+ New: Bitbucket Server Integration clones from upstream instead of mirror for newly created jobs in 3.2+
          Kristy Hughes made changes -
          Description Original: Bitbucket Server Integration plugin has a regression in 3.2.2 where it clones from the upstream server, even when configured to clone from the mirror.

          h3. Steps to reproduce:

          1. Create a job that is configured to clone from a mirror
          2. Build the job

          h3. Expected output

          * Job clones from the mirror

          h3. Actual output

          * If you inspect the console log, you will see that the job actually clones from the usptream.

          h4. Workaround

          This is not reproducible in 3.1.0.
          No known workaround.           		New: Bitbucket Server Integration plugin has a regression in 3.2.2 where it clones from the upstream server, even when configured to clone from the mirror for newly created jobs. Jobs created prior to 3.2 will continue to clone from the mirror.

          h3. Steps to reproduce:

          1. Upgrade Bitbucket Server Integration to 3.2
          2. Create a job that is configured to clone from a mirror
          3. Build the job

          h3. Expected output

          * Job clones from the mirror

          h3. Actual output

          * If you inspect the console log, you will see that the job actually clones from the usptream.

          h4. Workaround

          This is not reproducible in 3.1.0.
          No known workaround.
          Kristy Hughes made changes -
          Assignee New: Kristy Hughes [ khughes ]
          Kristy Hughes made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Atlassian Bitbucket Server made changes -
          Labels New: triaged
          Kristy Hughes made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Fixed but Unreleased [ 10203 ]

            khughes Kristy Hughes
            khughes Kristy Hughes
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: