Just in case anyone is following along at home…
On 01/08/2012, at 9:35 AM, Paul Hoadley wrote:
_However_, I'm not convinced this works reliably. I'm currently debugging a
situation where pushing commits to multiple Eclipse projects within the one
repo is triggering only the _first_ Jenkins
On 22/06/2012, at 9:04 AM, Paul Hoadley wrote:
I'm looking at moving some projects from Subversion to Git. We use Jenkins
as a build server. I'm interested to know some broad details about the
WO-Git-Jenkins setups that others are using.
In the past, we've used Subversion repositories
Hello,
I'm looking at moving some projects from Subversion to Git. We use Jenkins as
a build server. I'm interested to know some broad details about the
WO-Git-Jenkins setups that others are using.
In the past, we've used Subversion repositories that are somewhere in the
middle of the range
On 2012-06-21, at 4:34 PM, Paul Hoadley wrote:
Hello,
I'm looking at moving some projects from Subversion to Git. We use Jenkins
as a build server. I'm interested to know some broad details about the
WO-Git-Jenkins setups that others are using.
In the past, we've used Subversion
As you well know Paul, I don't have a Git-Jenkins setup (yet), but off the top
of my head, if I was concerned about the network latency and space consumption
of cloning a full git repo across the network for every Jenkins job execution,
I would approach my setup as follows:
(1) First, on the
On 22/06/2012, at 12:25 PM, Kieran Kelleher wrote:
As you well know Paul, I don't have a Git-Jenkins setup (yet), but off the
top of my head, if I was concerned about the network latency and space
consumption of cloning a full git repo across the network for every Jenkins
job execution, I
