Thanks. I guess I expected the headline job to work like a normal job, where changes are detected based on changes between the revision of the previous build.
On Tue., 14 Mar. 2017, 02:14 Simon Richter, <[email protected]> wrote: > Hi, > > On 13.03.2017 08:41, Daniel Becroft wrote: > > > 1. There is a checkout performed on the headline job; then > > 2. A checkout is performed for each individual job > > > Is there a way to remove the headline checkout as well, or a way to stop > > it being checked out to start with? > > That is normal. > > The headline job is responsible for deciding which version to build, and > it also maintains a list of changes for each build. The individual > builds don't check out the head revision, but rather the one that was > selected in the headline job -- that way, you get a consistent version > across all configurations. > > Simon > > -- > 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/c72138f6-431b-8820-907f-dc8e88133ddf%40hogyros.de > . > 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/CAJM0iSSDzAjCCEZX%3D3cDN%3DPYs_rYOShvS5i3HgmazYrzeFQ6Zg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
