Hi Les,
In my case, I'm not bothered by the actual build time, which is under 1
minute per solution. The problem is that the matrix build does a full
repository pull before each matrix element, when, in my case, it is
completely unnecessary, and adds 30+ minutes to the build time. Using
slave
On Tue, Aug 5, 2014 at 1:16 PM, Brian Moffat wrote:
> Hi Mark,
> The advantage of using my kludge as opposed to using a script to iterate
> through the builds is that Jenkins has all this great messaging (hipchat /
> email) and log capture that I would have to "re-implement". And I have a
> monito
Hi Mark,
The advantage of using my kludge as opposed to using a script to iterate
through the builds is that Jenkins has all this great messaging (hipchat /
email) and log capture that I would have to "re-implement". And I have a
monitoring/reporting infrastructure in place that is based on the
On Mon, Aug 4, 2014 at 3:02 PM, Brian Moffat wrote:
> Hi Mark,
> Ok - I can see that my use-case is not universal and is likely on the
> "very simple" end of the spectrum. I am currently not using distributed
> builds. My builds of multiple portals use the same code base and are
> serialized - t
Hi Mark,
Ok - I can see that my use-case is not universal and is likely on the "very
simple" end of the spectrum. I am currently not using distributed builds.
My builds of multiple portals use the same code base and are serialized -
therefore one checkout is all that is needed to build all of t
On Mon, Aug 4, 2014 at 12:24 PM, Brian Moffat wrote:
> Thanks Mark.
> I have a couple of follow-up questions, if you don't mind.
>
> 1. I've seen it work - meaning that the matrix project would do one
> checkout and the downstream projects would run one after the other with no
> lengthy pause be
Thanks Mark.
I have a couple of follow-up questions, if you don't mind.
1. I've seen it work - meaning that the matrix project would do one
checkout and the downstream projects would run one after the other with no
lengthy pause between. So I'm left feeling like there should be a way to
"get
On Mon, Aug 4, 2014 at 10:11 AM, Brian Moffat wrote:
> I have a matrix project to build different C# projects/solutions. There
> is one git repository for all solutions.
>
> The matrix job is configured for Git to checkout the master branch to a
> local directory, and then invokes a downstream p
I have a matrix project to build different C# projects/solutions. There is
one git repository for all solutions.
The matrix job is configured for Git to checkout the master branch to a
local directory, and then invokes a downstream project for each matrix
element (solution). That downstream p
