Multi-configuration has n+1 checkouts

[Daniel Becroft]

Good evening,

I've noticed something odd about the Multi-configuration jobs. There always seems to be N+1 checkouts performed (where N is the number of individual configurations). 

1. There is a checkout performed on the headline job; then

2. A checkout is performed for each individual job

When the individual configurations are run, I can configure the job to remove the workspace upon completion.

Is there a way to remove the headline checkout as well, or a way to stop it being checked out to start with?

Cheers,

Daniel B.

[Simon Richter]

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

[Daniel Becroft]

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.

--
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/c72138f6-431b-8820-907f-dc8e88133ddf%40hogyros.de.
For more options, visit https://groups.google.com/d/optout.

[Simon Richter]

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