Let me rephrase your question to make sure I understand.  You want to build a 
job only once a day, but this build may be triggered by SCM and if not then it 
should be triggered by the timer?  There isn't any way to do OR or AND 
statements between build triggers, which sounds exactly like what you want.  
One thing you could do is use the files found trigger, have A delete a file on 
master that C is polling for.  Then create a job, D, that is on a time trigger 
that writes to the same file on master and have this job run right after 
midnight.  With this setup, if there is an SCM change A will run and trigger B, 
and delete the file on master that C polls for, and B will trigger C to run.  
If there is no SCM change then D will create a file on master and C will find 
it in its polling which should be setup to be right before midnight, so it 
builds if there are no SCM changes.

What if there are multiple SCM changes in a day, do you still only want one 
build?

Will

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Gabor Lukacs
Sent: Monday, September 10, 2012 7:17 AM
To: jenkinsci-users@googlegroups.com
Subject: ignore triggers and do not insert job into build queue if the same job 
is running

Hello,
    exist a way to not add a job into build queue if the same job is currently 
running?
Config is simplified and is running once per day: A->B->C where C is triggered 
by upper job B or by time trigger, B is triggered by upper job A and A is 
triggered by SCM poll. If no change in SCM then A and B will not run, but will 
run C (because of time trigger, it takes the previous artifacts of A and B), 
but if exist some change in SCM then A and B will run, which then trigger and 
run C (longer run) and in this case I do not want to insert C into build queue 
(and run it) if time trigger occurs. I want to run C only once per day.

Thanks. With kind regards, Gabriel.

Reply via email to