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

upstream change in github plugin breaks tag fetching in github-branch-source

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • None

      Per https://wiki.jenkins.io/display/JENKINS/Git+Plugin Version 3.4.0 (July 17, 2017)

      • Because each branch job in a multibranch project will only ever build the one specific branch, the default behaviour for a Git Branch Source is now to use a minimal refspec corresponding to just the required branch. Tags will not be checked out by default. If you have a multibranch project that requires the full set of ref-specs (for example, you might have a pipeline that will use some analysis tool on the diff with some other branch) you can restore the previous behaviour by adding the "Advanced Clone Behaviours". Note: In some cases you may also need to add the "Specify ref specs" behaviour.

      However, the "Advanced clone behaviors" in git-branch-source instead reads "Do not fetch tags". Looks like the upstream change to the github plugin broke github-branch-source's behavior around tags.

            Unassigned Unassigned
            ahammond Andrew Hammond
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: