Slave Node associate to IP or User

2015-02-09 Thread uzqatester
Hi! I am creating a Jenkins Farm, i was looking the way to link an Slave Node to a User Credential or IP. What i need is that every developer execute the jobs in they virtual machine. How can I do this? Regards -- You received this message because you are subscribed to the Google Groups

Re: How to use Artifact Diff Plugin?

2015-02-09 Thread Burich Aleksei
Probably would be useful for someone. It works for me with the following steps: 1. Create job and in post-build actions add Archive Artifacts 2. Run your job several times 3. Go to your build and in the menu you'll find link 'Artifact Diff' 4. There you'll see table with last successfull,

RE: [workflow plugin] set build display name

2015-02-09 Thread Christoph Vogtländer
This does not work. build is not a property of WorkflowScript. Has this been implemented in a never version of the workflow plug in? I'm on Jenkins 1.580.3 LTS with Workflow plug in version 1.2. groovy.lang.MissingPropertyException: No such property: build for class: WorkflowScript at

RE: [workflow plugin] set build display name

2015-02-09 Thread Ginga, Dick
I'm sorry, from a build object call that method. build is a defined object in the Build Flow plugin I use. -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Christoph Vogtländer Sent: Monday, February 09, 2015 10:41 AM To:

Re: [workflow-plugin] Technical limitations for a workflow Groovy script

2015-02-09 Thread Timur Batyrshin
Hi, To allow certain signatures in Groovy Sandbox go to Manage Jenkins - In-process Script Approval. Please note that if you catch this kind of exceptions the signatures will not appear there. Timur суббота, 7 февраля 2015 г., 10:57:08 UTC+3 пользователь Baptiste Mathus написал: IIUC, for

Re: [workflow plugin] inject environment variables or using parameters to prepare the run

2015-02-09 Thread Timur Batyrshin
Hi Christoph, I use the plain Jenkins parameters for that, (checkmark for This build is parameterized). The parameters passed then appear inside the Groovy script as variables but not environment values. If you need to set env value you can do the following inside your Groovy script:

Re: workflow-plugin Serialisation issues when iterating over a list of strings

2015-02-09 Thread Daniel Beck
'each' is currently broken in Workflow CPS scripts. https://issues.jenkins-ci.org/browse/JENKINS-26481 On 09.02.2015, at 18:25, Brian Ray be_...@sbcglobal.net wrote: Hi Robin, The simplest Groovy idiom for iterating over a collection is hostnames.each { host - do something interesting

Build History widget: Can I change how many are shown

2015-02-09 Thread Steven Murphy
Hello, When navigating around my Jenkins dashboard it can sometimes be a bit slow when loading a projects main page. I think this may be down to the Build History widget, as when I minimize it the navigation becomes much quicker. Is there a way to reduce the number of builds that are display

Re: workflow-plugin Serialisation issues when iterating over a list of strings

2015-02-09 Thread Brian Ray
Hi Robin, The simplest Groovy idiom for iterating over a collection is hostnames.each { host - do something interesting with host ... } Does this work? Brian On Monday, February 9, 2015 at 5:48:11 AM UTC-8, Robin Tegg wrote: Hi all, I've been trying out the workflow plugin after

RE: Slave Node associate to IP or User

2015-02-09 Thread Rob Mandeville
I’m not sure what you mean. Are you saying that you want user ‘fred’ to be confined to the Jenkins slave on his own personal system? That wouldn’t be a Jenkins farm. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of uzqates...@gmail.com

Re: workflow-plugin Serialisation issues when iterating over a list of strings

2015-02-09 Thread Brian Ray
Another stab in the dark. The double quotes mean the individual hostnames are GStrings instead of Strings. Maybe starting this way: def hostnames = ['192.168.0.1', '192.168.0.2'] On Monday, February 9, 2015 at 9:25:52 AM UTC-8, Brian Ray wrote: Hi Robin, The simplest Groovy idiom for

workflow-plugin Serialisation issues when iterating over a list of strings

2015-02-09 Thread Robin Tegg
Hi all, I've been trying out the workflow plugin after watching the pimp-your-continuous-delivery-pipeline-with-jenkins-workflow-wjax-14 http://www.slideshare.net/cloudbees/pimp-your-continuous-delivery-pipeline-with-jenkins-workflow-wjax-14 demo. And in one of the slides (24), there is an

Re: Problem running Python Script, infinite wait? (MS Windows)

2015-02-09 Thread Maximiliano Santa Cruz
Ok, I finally made it work. What I did was to install the selenium grid plugin (Jenkins), installed a slave (Selenium Grid), and then executed a Windows Command (Jenkins) with my tests controller (which executes the automated tests in an ordered fashion). Doing that I was able to run the

RE: [workflow plugin] set build display name

2015-02-09 Thread Ginga, Dick
build.setDisplayName() -Original Message- From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Christoph Vogtländer Sent: Monday, February 09, 2015 9:32 AM To: Jenkinsci Users Subject: [workflow plugin] set build display name Hi, is it possible