Rob,
I have two different types of builds. One uses some prebuilt packages
("Project A") and the other builds everything including those packages that
are prebuilt ("Project B"). Since Project B takes more time to build I
don't want to run it very often.
I have Project A polling the SCM and building as it should. I would like
Project B to get queued when Project A builds and wait 8 hours for any
other changes that might take place. I don't want to run this big build for
every checkin. So what I want is for the first build of Project A to queue
a build of Project B and I don't want it to queue again until Project B
starts running.
So it would work like this:
9:00 Project A build #1 completes and Project B build #1 gets queued
(wait time of 8 hours)
9:48 Project A build #2 completes (nothing happens with Project B)
10:36 Project A build #3 completes (nothing happens with Project B)
1:05 Project A build #4 completes (nothing happens with Project B)
5:00 Project B build #1 starts
5:01 Project A build #5 completes and Project B build #2 gets queued
Yes, this question is somewhat related to my other question in that Project
B will never build if I configure it to be a post-build action of Project A
with a quiet period of 8 hours.
I believe the other question applies to are more common scenario though. I
don't want my builds to be queued infinitely.
Thanks for your help,
Lewis
On Thursday, June 14, 2012 12:01:50 PM UTC-7, Lewis wrote:
>
> I would like to have Project A trigger a build of Project B with a very
> large wait time (about 8 hours).
> I do not want the project to reset it's wait time if Project A builds.
>
> Instead of trying to queue the project again and resetting the wait time I
> would like Jenkins to realize
> that the project is already in the queue and ignore it.
>
> Is there a known way to do this?
>
> -Lewis
>
