Hi Jason,
Thanks for this suggestion - this looks like it will work for us!
--Jim
On Tue, May 28, 2013 at 3:10 PM, Jason Swager wrote:
> Your second approach - slightly modified - would work. Create a job that
> determines if the next job should run, using whatever logic/scripts you
> want.
On Tue, May 28, 2013 at 2:03 PM, Jim Zajkowski wrote:
>
> This is perhaps a bit outside the normal Jenkins setup, but I need to have a
> job run periodically, and that job will determine whether or not another job
> should be run.
>
> Right now I have this working by having the first job change a
Your second approach - slightly modified - would work. Create a job that
determines if the next job should run, using whatever logic/scripts you
want. If you want to trigger the next job, write out a file. Then use the
Conditional Build Step plugin (
https://wiki.jenkins-ci.org/display/JENKIN
Hi all,
This is perhaps a bit outside the normal Jenkins setup, but I need to have
a job run periodically, and that job will determine whether or not another
job should be run.
Right now I have this working by having the first job change a file and the
second job trigger via FSTrigger.
Howeve
