I have a job which is pretty resource intensive.
That's why i want it to be executed only when all upstream jobs are stable.
Therefore I prepended a groovy script action to the job (original action
now #2).
The groovy script checks that all upstream jobs are stable.
But I am unable to stop the bu
corresponding API exists currently?
Than I would fill an enhancement request to add that kind of method to the
a build.
- Dirk
On Wednesday, October 24, 2012 11:24:10 AM UTC-7, dthomas wrote:
>
> I have a job which is pretty resource intensive.
> That's why i want it to be executed only whe
In version 1.482 the feature "Report root causes of UpstreamCause in log
and status pages" has been added. In certain scenarios (as stated
below) this is absolutely not feasible because the amount of data logged
per build might become dozens of megabytes. The result is that the jobs
folder grow
Is there any way to get the attention of the developers to address this
pretty severe issue?
https://issues.jenkins-ci.org/browse/JENKINS-15747
- Dirk
I have two projects A and B where B is a downstream project of A.
When A is triggered while B is still building I would like to automatically
abort the current run of B since the result is no more useful and it will
be re-triggered soon anyway.
Is there a way to achieve that in Jenkins?
Thanks,
-
