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 different checkouts of the the
> repository?
You don't _have_ to, but normally, the point of a build is to build a
component or application, not a bunch of unrelated stuff. So for most
people it doesn't make any sense to check out anything but exactly the
revision you want at exactly the top-level directory containing the
code you want to build. And jenkin's repository pollers will then
correctly track new commits and build the right things automatically
when you do it that way.
It rarely makes any sense to check out a whole repository that is
likely to contain tags/branches, etc. that are unrelated to your
current build.
--
Les Mikesell
lesmikes...@gmail.com
