Re: Multi-configuration has n+1 checkouts

2017-03-14 Thread 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

Re: Multi-configuration has n+1 checkouts

2017-03-14 Thread 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. On Tue., 14 Mar. 2017, 02:14 Simon Richter, wrote: > Hi, > > On 13.03.2017 08:41, Daniel Becroft wrote: > > > 1. There is a checkout perf

Re: Multi-configuration has n+1 checkouts

2017-03-13 Thread 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

Multi-configuration has n+1 checkouts

2017-03-13 Thread 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