Hi, On Sun, Aug 26, 2012 at 9:56 AM, Sami Tikka <sjti...@gmail.com> wrote:
>> I always thought you have to specify polling schedule if you check the >> polling box... but you can make the polling cycle very long, e.g. once a >> week. On 26/08/2012, at 4:52 PM, Richard Bywater wrote: > Nope - just ticking the box and leaving the schedule blank works a > charm. No need to have that build for no reason :) I can certainly confirm that it works... when it works. But this does seem to be a bug: >>> The problem is that when I push changes that span multiple projects in the >>> repo, only one of the projects is being built. If it's the wrong project >>> with respect to dependency order, the build breaks. This seems to happen >>> regularly, but I don't know whether it's deterministic. It's certainly >>> breaking the build often enough to be very annoying. In any case: > On Sun, Aug 26, 2012 at 9:56 AM, Sami Tikka <sjti...@gmail.com> wrote: >> Neither Jenkins or Git really support having multiple projects in one Git >> repository (at least not yet). The difficulties you are experiencing are a >> result of that. I think I finally agree. I've split the repo in four, and have re-organised Jenkins to build one-project-per-repo. I think the upside here is much greater than the downside. (Where the downside is that the projects were genuinely fairly closely coupled. I would regularly push changesets for, say, some feature that spanned more than one of them. Now those will have to be multiple commits across multiple repos. But I can live with that.) -- Paul.
