Can't you make it dependent on the configuration? Like that you would only fire a build after the configuration was pushed, which, hopefully, refers to packages that actually exist :)
cami On 2011-10-24, at 13:15, Igor Stasenko wrote: > On 24 October 2011 11:23, Mariano Martinez Peck <[email protected]> wrote: >> Marcus, the problem is that jenkis is working VERY well ;) Now, really, >> the thing is that I have a lot of packages, and when I change in several of >> them, when I commit the first package, Jenkis automatically fires up a >> build. That happens even before I can commit the rest of the packages. >> Hence...the build become unstabe, and just in the next build it becomes >> stable again... >> So...I was wondering, maybe we can put kind of delay ? so that Jenkis does >> not trigger a build immediatly, but say, after 5 minutes? (that gives me >> time to commit all packages) >> > > The solution is simple, as to me: > Do not commit the first, before you commit the rest :) > > Apparently, if jenkins watching for changes in PackageA, which depends > on PackageB, > first you should commit B, and only then A. > >> Thanks >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > > > > -- > Best regards, > Igor Stasenko. >
