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 job. Obviously that can be > disastrous if the project dependency is the other way around. (I haven't got > to the bottom of it yet—something like that is happening, though I can't > prove it's the fault of Jenkins.) I was able to reproduce this at will. Say you have FooApplication dependent on FooFramework, and they're both in the Foo repository. (I'm using Bitbucket, but I presume that doesn't matter.) FooApplication and FooFramework are both Jenkins jobs, with the latter triggering the former. You can restrict FooApplication to just be triggered by commits to "FooApplication/.*", and similarly with the framework, which is nice in theory. I had polling set to 5 minutes. Pushing commits just to FooFramework triggered that project to build, as expected. But pushing a group of commits that included commits to _both_ projects triggered a build in only _FooApplication_, and it was reproducible. A workaround is to use some sort of push notification from the repository, and this is what I have done. (Simple polling was nicer, as you can keep your Jenkins server isolated from inbound traffic.) -- Paul Hoadley http://logicsquad.net/
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
