I got super-confused here for a minute, so I thought it might be worth pointing out that people who are using multibranch pipelines can completely ignore the article presented in this thread (it says it's for "non-multibranch jobs") and get this bitbucket server add-on instead: https://marketplace.atlassian.com/plugins/nl.topicus.bitbucket.bitbucket-webhooks/server/overview. stephen has recently submitted pull requests for this "topicus" add-on, so i'm pretty sure it's still a thing. :) it works in concert with the Bitbucket Branch Source jenkins plugin.
On Wednesday, June 7, 2017 at 11:29:09 PM UTC-4, Mark Waite wrote: > > > > On Wed, Jun 7, 2017 at 5:46 PM Stephen Connolly <[email protected] > <javascript:>> wrote: > >> On Wed 7 Jun 2017 at 22:48, Łukasz Zachulski <[email protected] >> <javascript:>> wrote: >> >>> I've found Jenkins article Triggering a build using hooks in Bitbucket >>> server >>> <https://support.cloudbees.com/hc/en-us/articles/226568007-Triggering-a-build-using-hooks-in-Bitbucket-server> >>> >>> and it states that >>> >>> You need to ensure that your workspace is not deleted after every build. >>>> The Git plugin needs the workspace in order to compare previous commits to >>>> check if there were changes in the repository or not. >>> >>> >>> > As far as I understand it, that statement is incorrect. The git plugin > does not need the workspace to check if there were changes in the > repository or not. The plugin remembers the SHA1 associated with a build. > If a SHA1 is detected which has not been previously built, then it is > assumed a new build is needed. > > Remote polling (the default) does not require a workspace, unless you're > using certain special cases, like ignoring commits based on the commit > author or commit message. > > Mark Waite > > >> What will happen if the workspace will be deleted or when build will be >>> simply executed on different node? Will Jenkins not be able to correctly >>> depict changes between previous and current builds? >>> >>> > Changes from build to build are calculated using the git repository that > was used for the build. That repository is assumed to have enough history > in it to compute the differences between the build and its predecessor. > > Yes, it is possible to violate that assumption using a shallow clone value > that is less than the number of intervening commits between the build and > its predecessor. > > No, I haven't tested the behavior when that assumption is violated. > > Mark Waite > > >> How does this rule apply to *Pipeline*, especially *Multibranch* and >> *Bitbucket >>> Team* jobs and the fact that mult-ibranch jobs do it own branch >>> indexing? >>> >> >> Multibranch keeps its own track. You can ignore that rule for multibranch >> >>> >>> >>> With Regards, >>> Lukasz. >>> >>> -- >>> 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 [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/2060c2f6-78a9-4421-a15d-aabafb3877d8%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/2060c2f6-78a9-4421-a15d-aabafb3877d8%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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwj%3DwH1-ue599HspTL8vkDzTYCfjJjM%3DBWbZF6CrK0t0A%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwj%3DwH1-ue599HspTL8vkDzTYCfjJjM%3DBWbZF6CrK0t0A%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/07e9deec-a0ab-45ce-8ec6-a08db28cc93f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
