On Wed 7 Jun 2017 at 22:48, Łukasz Zachulski <[email protected]> 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. > > > 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? > > 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]. > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwj%3DwH1-ue599HspTL8vkDzTYCfjJjM%3DBWbZF6CrK0t0A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
