Hello all,
I've just read the official jenkins book which gave me some ideas,
but I wanted to flesh out my ideas before I start configuring.
We have a relatively complex system which looks like this:
// old code bases, actively used elsewhere, but not actively changed
A - svn repo, updated
My initial guess on how to solve this:
* put each of the repo's in a job that *only fetches* the repo into a
shared directory and doesn't do anything else.
I'd think in terms of jobs that build components and applications, not
so much in relationships to repositories.
The problem is that
On Mon, Jun 4, 2012 at 9:13 AM, Bram de Jong bram.dej...@samplesumo.com wrote:
On Mon, Jun 4, 2012 at 5:27 PM, Bram de Jong bram.dej...@samplesumo.com
wrote:
My initial guess on how to solve this:
* put each of the repo's in a job that *only fetches* the repo into a
shared directory and
On Mon, Jun 4, 2012 at 11:13 AM, Bram de Jong
bram.dej...@samplesumo.com wrote:
I suppose the gist of my question is:
If I have 50 different applications that are all sitting in the same
repository, and I want each of these applications to build separately
as a job, do I really need to do 50
On Mon, Jun 4, 2012 at 11:48 AM, Bram de Jong
bram.dej...@samplesumo.com wrote:
If you'd go back to my first email and substitute repository by
trunk maybe my emails make more sense?
Our apps don't need the full repositories, they just need the trunk/master.
But still, the rest of my email(s)
