Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#2967 closed support-request (fixed)

builder dependancy

Reported by: sachinpatela Owned by:
Priority: blocker Milestone: undecided
Version: 0.8.7 Keywords:

Description (last modified by sa2ajj)

Hello I am currently trying on system where all builders (waterfall column) started at same time on same revision But here I have just one build to track other builds and wait for all others builders on same revision to finish

  • How this could be achievable currently I can't see any way for doing this
  • Also this tracking builder should also able to start new builds as new revision comes in and other builders should be able to start running with this revision after they finish previous build.
  • how to achieve if one builder is forced using forcescheduler it should also automatically force some other builder


Attachments (2)

snapshot5.png (112.9 KB) - added by sachinpatela 6 years ago.
snapshot6.png (92.0 KB) - added by sachinpatela 6 years ago.

Download all attachments as: .zip

Change History (14)

comment:1 Changed 6 years ago by Ben

You are probably looking for the Triggerable Scheduler / Trigger step.

comment:2 Changed 6 years ago by sachinpatela

Sorry ! what I mean is All builders triggered at same revision but they will be starting at different time like Nightly triggerable So one builder could trigger all other but all these other could start at different time and will be finishing at different time and triggering build should wait for all builds started for this particular revision But could still be able to trigger multiple revisions


comment:3 Changed 6 years ago by tardyp

  • Priority changed from blocker to minor

Hi sachinpatela,

Your problem is really about a TriggerStep? with waitForFinish=True.

the Triggered build inherit the sourcestamp, so if you are using a source step supporting those, then you will build the correct version, even if there are some delays due to build queues.

comment:4 Changed 6 years ago by sachinpatela


I am using singlebranchscheduler for triggering builder for main builder then nightlytriggerable for remaining builders

I tried trigger and triggerable combination with waitforfinsh=true while adding trigger for remaining builds then these builders run sequentially rather than parallel Also this is not giving me capability of nightly run


comment:5 Changed 6 years ago by sachinpatela

For NightlyTriggered? Scheduler Documentation says : This class is only useful in conjunction with the Trigger step. Note that waitForFinish is ignored by Trigger steps targeting this scheduler.

My setup is singlebranchscheduler triggered "builder0" this builder has 10 triggered steps for builder1..builder10 each of these builders using NightlyTriggerable? with different day and time settings.

I tried to set waitforfinish=True for trigger steps of builder1..builder10 which started running properly on specified time but Builder0 did not wait for these to finish and exited immediately after executing trigger and other its own steps


comment:6 Changed 6 years ago by sachinpatela

  • Priority changed from minor to blocker

Changed 6 years ago by sachinpatela


comment:7 Changed 6 years ago by sachinpatela

Here is attached snapshot Topverification is triggered by singlebranchscheduler at 17:29:32 @=sachin.patel changes which triggered TopV-TestSS-JTAG TopV-TestSS-DDR3 @17:32:16

Both triggered TopV-TestSS-JTAG TopV-TestSS-DDR3 schedule to run at 17:34 by Nightlytriggerable which they started But Tovpverification did not wait them to finish and finished just after triggering @ 17:34:00

comment:8 Changed 6 years ago by tardyp

You have two trigger steps.

You should rather put only one step, and thus trigger two Triggereable schedulers in the same step.

Changed 6 years ago by sachinpatela

comment:9 Changed 6 years ago by sachinpatela

Added single trigger step triggering 2 builders which are nightytriggerable As you cam see in latest attachment snapshot6 there is no difference Topverification is still not waiting other 2 to finish


comment:10 Changed 6 years ago by tardyp

indeed, NightlyTriggerable?, is a new thing I am not entirely familiar with.

This scheduler is not meant to be waited for. It is meant to only create build at a certain point of time, but based on the sourcestamp from another build. The doc is correct, it does not make much sense to be waited at.

By reading again the thread, I am not sure of the problem you are trying to tackle. I would say it may make sense to do more separation of concerns, e.g create 2 builders for the 2 usecases (force, and automatic), and/or 2 schedulers.

comment:11 Changed 6 years ago by sachinpatela

  • Resolution set to fixed
  • Status changed from new to closed

comment:12 Changed 6 years ago by sa2ajj

  • Description modified (diff)
Note: See TracTickets for help on using tickets.