Hi, On 14.03.2017 12:20, Daniel Becroft wrote:
> 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. The headline job is the normal job. It determines whether a build is required, does a checkout and copies the new log entries to the change log for the build, as any other job would do. The individual builds ignore the branch configuration and just check out the version that the headline job selected, then generate the change log as a regular job would do (which should have the same entries as for the headline job). If you have artifacts, changes in artifacts are only recorded in sub-jobs, because these are detected during the build steps (which are ignored in the headline job). 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/94a33c78-f6ab-8b25-e877-1ea858899c37%40hogyros.de. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
