quotes in bash script on windows are being ignored

Hi, I have a jenkins project whose "Execute shell" command consists of this: set -e # Exit immediately if a simple command exits with a non-zero status set -x verbose export PKG="annotation" export SUFFIX="zip" ssh -o StrictHostKeyChecking=no -i $SSH_KEY jenk...@docbuilder.mydomain.org "rm

unable to connect slaves (behind firewalls) to master (in cloud) - this used to work

Hello, Previously I had a Jenkins master running on an EC2 instance in the Amazon cloud, and two slave nodes, one of which was also in EC2 and the other of which is here at my institution, behind a firewall. Both slaves connected to the master using Java Web Start and everything worked fine. N

Re: incorrect parameters passed to downstream build with Parameterized Trigger plugin

en run using the copy artifact plugin. > This normally removes other issues related to using the same workspace for > multiple jobs, when they get out of sync i.e. when job B only runs once for > multiple runs of job A. > > Chris. > > On Wednesday, 15 May 2013 00:03:56 UTC+

incorrect parameters passed to downstream build with Parameterized Trigger plugin

Hi, I have two multi-configuration projects, A and B. Each job is configured to run on the same three nodes: the master (linux) and mac and windows slaves. Project A is set up to trigger a build of B when A builds successfully, passing it the following predefined parameters (using the Parameter

Re: downstream job set by Parameterized Trigger never runs

On Tuesday, May 14, 2013 10:09:23 AM UTC-7, Dan Tenenbaum wrote: > > Hi, > > I'm using the Parameterized Trigger plugin. I have a multi-configuration > project (project A) which has a post-build action to "Trigger parameterized > build on other projects"

downstream job set by Parameterized Trigger never runs

Hi, I'm using the Parameterized Trigger plugin. I have a multi-configuration project (project A) which has a post-build action to "Trigger parameterized build on other projects", configured to run another multi-configuration project (project B) when the build is stable, and pass B the current b

Re: difficulty connecting to Mac slave

Url http://master:8080/computer/slave/slave-agent.jnlp -secret And in fact I could start this command with 'nohup' and pipe its output to a file (and put & on the end of it) and I don't need to be logged in on the slave for my builds to work. I'll set up this command to be r

Re: difficulty connecting to Mac slave

is > fairly simple to do using NetBeans: > https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/9a4F7jN1JNI > I'll try it if other avenues don't work out. Thanks, Dan > Hope this helps some, > > Kenny > > > On Wednesday, May 1, 2013 4:47:46 PM UT

Re: difficulty connecting to Mac slave

On Wed, May 1, 2013 at 10:04 AM, Dan Tenenbaum wrote: > On Tue, Apr 30, 2013 at 6:49 PM, Kenny Ayers > wrote: >> You're experiencing at least two issues here. First there's the OSX bug >> with your window manager permissions. You need to run headless on OSX, as &

Re: difficulty connecting to Mac slave

Have you tried a combination of SSH + running > headless (perhaps that was your error message you included)? > > I hope this helps, > > Kenny > > On Tuesday, April 30, 2013 5:28:11 PM UTC-7, Dan Tenenbaum wrote: >> >> Hi all, >> >> I have tried a numbe

Re: difficulty connecting to Mac slave

> Scott > > > On Tue, Apr 30, 2013 at 7:28 PM, Dan Tenenbaum wrote: >> >> Hi all, >> >> I have tried a number of methods to connect to a Mac slave and have had no >> success. >> >> My master is also a mac and it's called dhcp151178

difficulty connecting to Mac slave

Hi all, I have tried a number of methods to connect to a Mac slave and have had no success. My master is also a mac and it's called dhcp151178. The slave I'm trying to connect to is called pelham. These of course are machines on my internal network. The first method I tried was "Launch slave