On Tuesday, 21 January 2014 17:02:55 UTC, MoBarger wrote:
Hi - just curious if anyone here has implemented JE.
Yes - many have (including me)
Can same
functionality be achieved with free plugins instead of going with the
paid versions that Cloudbees offers?
No. Some of it can -
Due to the slowness of the UI with my 1.532.1 I will give a try to the 1.532.2
RC (20140113)
I'll let you know if its better
On Sat, Jan 18, 2014 at 12:40 AM, Daniel Beck m...@beckweb.net wrote:
On 18.01.2014, at 00:32, Les Mikesell lesmikes...@gmail.com wrote:
Is there a changelog for
Hi Daniel
Except that Matrix parent jobs are lightweight since 1.337, which means its
executors are created dynamically on demand.
Thanks very much for this information.
Best regards
David
-Original Message-
From: jenkinsci-users@googlegroups.com
I was able to jiggle the config back into submission with a
combination of backups and edits to remove the plugin calls manually.
Hope this helps someone someday :)
On Thu, Jan 23, 2014 at 5:17 AM, Maureen Barger mobar...@gmail.com wrote:
Running LTS 1.532.1
I tested these plugins in a
Jenkins experts,
Does anybody remember how to pass variable from shell execution inside the job
to Jenkins itself?
Say there is pre-step:
varID=(grep something ${WORKSPACE}/pom.xml | cut something else)
Is it possible to use $varID in further non-shell steps in the job?
--Roman
I think you can write things to a file from your shell, then make the next
build step Inject environment variables plugin and those values are now
available to build steps and other shell steps.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of
We've got a technique for this at our shop. It requires the envInject plugin.
You write a line such as:
echo varID = $varID export_props.properties
In the step after the shell step, create an Inject environment variables step
that reads from export_props.properties.
Now, the contents of
MachineA is not a Jenkins slave but rather my test target (I test specific
software on a specific hardware platform).
Or, I’ve misunderstood your question. I have only a single Jenkins instance
with several executors.
Thank you.
On Jan 23, 2014, at 10:18 AM, matthew.web...@diamond.ac.uk
We do this as well FWIW.
On Thu, Jan 23, 2014 at 10:55 AM, Mandeville, Rob rmandevi...@litle.com wrote:
We’ve got a technique for this at our shop. It requires the envInject
plugin.
You write a line such as:
echo “varID = $varID” export_props.properties
In the step after the shell
Yup, just checked and it works just fine. Gonna be doing a lot of this from now
on :)
Thank you,
--Roman
On 2014/01/23 12:48 PM, Maureen Barger wrote:
We do this as well FWIW.
On Thu, Jan 23, 2014 at 10:55 AM, Mandeville, Rob
rmandevi...@litle.commailto:rmandevi...@litle.com wrote:
We’ve
This problem can be solved simply with the Exclusion plugin.
- Original Message -
From: jenkinsci-users@googlegroups.com
To: jenkinsci-users@googlegroups.com
At: Jan 23 2014 12:11:25
MachineA is not a Jenkins slave but rather my test target (I test specific
software on a specific
11 matches
Mail list logo
