On Thu 31 Aug 2017 at 08:44, Sverre Moe <sverre....@gmail.com> wrote:
> From the release note it says it can be added with "Advanced Clone > Behaviours". > > > - 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. > > > > Next time I update my Jenkins plugins I am going to take extra care to > make sure there is no braking changes. > You were relying on unspecified behaviour that was contrary to the original design (granted my documentation of the original core principles is probably hard to find, but the 2013 view of SCMSource was *minimal* checkout by default) I appreciate that from your PoV it doesn't matter if I wrote down somewhere 4 years ago that the checkout should be minimal, it's still a breaking change from your PoV, but we have other users complaining that the checkouts are too big, and the defaults should be opinionated and tuned for the majority first. Sorry that you got bit by this one. The SCMSource implementations are now - IMHO - aligned with the original and current design, so going forward I do not anticipate further big changes. HTH > > onsdag 30. august 2017 17.21.11 UTC+2 skrev Mark Waite følgende: > >> Refer to the git plugin release notes for git plugin version 3.4.0. >> >> You can restore the original behavior to request the tags (and to not >> honor refspec on initial clone) by adding the Advanced checkout options to >> the job definition. >> >> Mark Waite >> >> On Wed, Aug 30, 2017 at 2:00 AM Sverre Moe <sverr...@gmail.com> wrote: >> > Have pipeline changed how it does checkout scm recently? >>> Previously I got tags with each checkout, but no longer. >>> I have to execute shell script 'git fetch --tags" after calling checkout >>> scm. >>> Makes me wonder what has changed, what else might have changed and how >>> can I get back the previous behaviour. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to jenkinsci-use...@googlegroups.com. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/c53ec2ae-d663-4a20-84ce-ab9e005f2255%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/c53ec2ae-d663-4a20-84ce-ab9e005f2255%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/f5b5dcdb-5220-40d6-a3f2-fd6a105e7c77%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/f5b5dcdb-5220-40d6-a3f2-fd6a105e7c77%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMyyx4B%3DkF93Yvey-NgnyfC%2BE44RKa_oR682dtge1n%3DD8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
