Re: Script behaves differently when run through Jenkins

2012-11-01 Thread Burkhard Reffeling
urceController.execute&entity=method> at hudson.model.Executor.run(Executor.java:239) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method> * * *Burkhard Reffeling* Software Engineer On 1 November 2012 17:51, Burkhard Reffeling wrote: > Haha ;) I

Re: Script behaves differently when run through Jenkins

2012-11-01 Thread Burkhard Reffeling
el.ResourceController.execute(ResourceController.java:88) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method> at hudson.model.Executor.run(Executor.java:239) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.r

Re: Script behaves differently when run through Jenkins

2012-11-01 Thread Burkhard Reffeling
Thanks, I'll give it a spin tonight (don't use windows, so shouldn't be a problem) * * *Burkhard Reffeling* Software Engineer On 1 November 2012 12:44, Stephen Connolly wrote: > I actually have the ssh-agent plugin version 0.2 now no-longer requiring > tomcat-nati

Re: Script behaves differently when run through Jenkins

2012-10-31 Thread Burkhard Reffeling
b [MY PUBLIC KEY ...] * * *Burkhard Reffeling* Software Engineer On 31 October 2012 17:02, Vincent Latombe wrote: > Hi, > > you should check that the HOME variable is defined and accessible to the > Jenkins process (or to the slave that is executing the task). I remember > having the same ki

Script behaves differently when run through Jenkins

2012-10-31 Thread Burkhard Reffeling
Hi all, I've got a Jenkins build that runs a Capistrano deploy as a post-build action. Running the Capistrano task as the Jenkins user from the console works absolutely fine and without a password prompt (I've previously set up SSH keys on both build and staging server). However, when running