Gianluca,
Perfect. I'll look into this.
Thanks,
Chris
On Tuesday, September 15, 2020 at 11:26:48 AM UTC-4 Gianluca wrote:
> Yes, it explains.
>
> I would suggest to use intermediate artifacts / published files to use on
> the "Deploy" job to know what to do instead of trigger that from
Yes, it explains.
I would suggest to use intermediate artifacts / published files to use on
the "Deploy" job to know what to do instead of trigger that from "Build"
job.
(I'm calling "Build" the one that runs on mid-day and "Deploy" the one that
runs at "H 21 * * 1")
So, in my suggestion the
At 17:07 15.09.2020, zil...@gmail.com wrote:
>Hi Fabi,
>
>Great idea. How can JobA set a flag for JobB that persists when JobB runs at
>9:00pm ET?
That depends on your system. I don't know if there's a Jenkins internal
way to do this. But if the jobs run on the same machine then maybe
you could
Fabi,
Using this
trick?
https://www.quora.com/How-can-I-pass-a-parameter-from-one-job-to-another-in-Jenkins-using-property-file
On Tuesday, September 15, 2020 at 11:07:18 AM UTC-4 zil...@gmail.com wrote:
> Hi Fabi,
>
> Great idea. How can JobA set a flag for JobB that persists when JobB runs
Hi Fabi,
Great idea. How can JobA set a flag for JobB that persists when JobB runs
at 9:00pm ET?
On Tuesday, September 15, 2020 at 10:56:48 AM UTC-4 fcenedese wrote:
>
> >...but I wish I can do this (for illustration only, the cron option does
> not exist of course)
> >
> >Step in JobA to
Thanks for responding Gianluca.
So I have a Jenkins job that builds production code mid-day, but does NOT
deploy it. We have a a separate deployment job that's cron'ed at "H 21 * *
1" to deploy the code built by the mid-day build job
Part of the mid-day build is to check if certain
>...but I wish I can do this (for illustration only, the cron option does not
>exist of course)
>
>Step in JobA to trigger JobB to run around 9:00pm ET
>build job: JobB,
> cron: "H 21 * * 1",
> wait: true
How about JobB always runs at 9 (started from cron)
and always checks first,
>From what I know that's specific thing is not possible.
And to be honest, it's quite strange as well.
Maybe if you explain us why are you trying to do that, we could suggest
alternatives that are possible in Jenkins.
Cheers,
Gianluca.
Il giorno martedì 15 settembre 2020 alle 15:40:20 UTC+1
I see this, but I don't understand how to implement it for my use case.
https://www.codependentcodr.com/scheduled-builds-in-jenkins-scripted-pipelines.html
I want JobA to trigger JobB, but at a certain time. I do this now
*Step in JobA to trigger JobB*
build job: JobB,
wait: true
...but I
