It is said that jenkins 2.x should be backwards compatible so I not really sure
why buildflow break the gui. For me it only dissapear when navigating using the
tab, so scrolling usually works.
Right now I do not consider pipeline mature enough for use in production but
you may be of other
Hi
You could add a slave with one executor on each of the physical servers that
handle only the restricted builds.
//stefan
> 4 mar 2016 kl. 22:09 skrev Tom Fitzhenry :
>
> A less-than-ideal-but-possibly-okay solution is:
> 1. Set one of the build slaves to 'Only
Hi,
>From my experience Build flow do not throw an exception if the build is
>aborted, unstable or failed, assuming the build actually started and completed
>normally.
I assume you have checked what exception was caught.
> 3 dec 2015 kl. 10:51 skrev Valeriy Leykin :
>
>
Hi,
And as always with buildflow, make sure that the "use workspace" is enabled in
the job configuration.
Since the environment variable seem to be created by envinject plugin.
//stefan
> 1 nov 2015 kl. 13:21 skrev GS_L :
>
> The problem is that the EnvInject isn't
Hi,
Doesn't this work?
build.environment["BUILD_CAUSE"]
Atleast this works for me for manually started builds. However it will not get
the real cause if it is started by upstream jobs
> 1 nov 2015 kl. 13:21 skrev GS_L :
>
> The problem is that the EnvInject isn't
(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43)
Stefan Thomasson answered:
I am not sure that this is what cause the error but I think you
forgot a comma between the two ignores
Thanks for the reply
Hi,
I am not sure that this is what cause the error but I think you forgot a comma
between the two ignores
13 jun 2015 kl. 02:49 skrev CLOSE Dave dave.cl...@us.thalesgroup.com:
I have a Jenkins job using the build flow plugin. A portion of it looks
like the code below.
parallel (
{
Hi,
If i understood your description, i am wondering if this Isn't the expected
behaviour for buildflow as it is a fly weight job and therefore do not
consume any executors?
5 mar 2015 kl. 23:39 skrev Ty Satrang ty.satr...@gmail.com:
I am not sure how you want to receive that, but here is a
Hi,
I am also wondering about this, it does not help restarting jenkins as the jobs
are resumed automatically.
For me it was caused by starting the same job with identical parameters.
19 feb 2015 kl. 19:11 skrev Chris Taclas ctac...@gmail.com:
Hi all,
I have a jenkins job set up using
Hi
If this only happens when a lot of simultaneous jobs are running on the same
node you may want to check if you are reaching one of the limits set by ulimit,
like threads per user.
http://stackoverflow.com/questions/5253072/java-unable-to-create-new-native-thread
//stefan
5 jan 2015 kl.
10 matches
Mail list logo