Hi there,
I have defined a parallel build using the build-flow plugin [1]:
-- 8 --
revision = build.properties[environment][GIT_COMMIT]
parallel (
{ build(rspec, GIT_COMMIT: revision) },
{ build(cucumber-backend, GIT_COMMIT: revision) }
)
-- 8 --
Both dependent build generate test
I am admittedly a novice at Groovy but this script does not complain about the
put operation but does not apparently perform it:
label-name is a parameter in that build.
[cid:image001.png@01CFEDFD.3809F840]
Dick Ginga, Informatics RD
PerkinElmer Inc. | For the Better
HUMAN HEALTH |
Has nothing to do with Groovy. You always get a fresh copy of the build
environment:
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractBuild.java#L1009
getEnvironments() is probably what you want.
On 22.10.2014, at 19:36, Ginga, Dick
I think the variables set on a completed build are probably read-only. If
you're looking to pull the last build's variables, modify, then re-use
them, you probably want something like:
def newvars = build.buildVariables.clone()
etc...
On Wed, Oct 22, 2014 at 10:36 AM, Ginga, Dick
Last time I looked at the code jobs run from the build flow don’t actually show
up as downstream jobs – so the report aggregation is working flawlessly and
aggregating all downstream jobs (which is no jobs).
So it’s not a configuration issue – but a code issue.
Regards,
/James
From:
This is my experiment, I am actually trying to do this is a post-build Groovy
step.
What I am “actually” trying to do is change or create a build variable in
either a Build Flow step or a post-build groovy step so that it is available to
a subsequent post build step. I am doing this now by
It's true - you can't actually update a parameter list in-place. You
have to create a new one to replace the old one. Here's how I did it,
based on some code I found from a 2012 question
https://groups.google.com/forum/#%21topic/jenkinsci-users/szhuDfCvpiE
on this group. This code will update
On Wed, Oct 22, 2014 at 8:21 PM, James Nord (jnord) jn...@cisco.com wrote:
Last time I looked at the code jobs run from the build flow don’t
actually show up as downstream jobs – so the report aggregation is working
flawlessly and aggregating all downstream jobs (which is no jobs).
So
Hi,
We would like to have something scanning our jobs' console output, looking
for Use of uninitialized and highlighting it for us.
I first thought of using the Log Parser plugin, which we're using
elsewhere, so I could make a build unstable if it sees it; however, our
jobs generally report test
Hi,
have you solved this issue? We have the exact same issue.
Thanks,
Andras
On Friday, May 23, 2014 8:07:17 AM UTC-7, Guillaume Boucherie wrote:
Hi,
I made more tests and I find something very interesting.
When I launch the slave with a custom script the communication between
master and
Do you have any logs? In http://your_jenkins_url/log and jenkins.log ?
On Friday, May 23, 2014 6:07:17 PM UTC+3, Guillaume Boucherie wrote:
Hi,
I made more tests and I find something very interesting.
When I launch the slave with a custom script the communication between
master and slave
Hi
I reboot node machine at the end of build setup, using “Execute Windows batch
command”:
powershell -command Start-Sleep -s 120
shutdown –r
This works only build is successful, because build stops where failure
occurred, before above lines are executed.
How can I reboot windows node machine
For me it was link to linux kernel used. See this bug for more information
: https://issues.jenkins-ci.org/browse/JENKINS-14332
Regards
Guillaume Boucherie
Guillaume
2014-10-22 23:05 GMT+02:00 Kanstantsin Shautsou kanstantsin@gmail.com:
Do you have any logs? In
13 matches
Mail list logo
