Found it by looking in the jenkins log. Kept getting an exception related
to a workspace. There was none. Forced the job to run once and create the
workspace, now everything works great.
Greg
On Thursday, October 30, 2014 9:49:28 PM UTC-4, Greg Dickie wrote:
>
> Hi,
>
> I was usin
Adding info to my own post.
After adding some tracing it looks like things go wrong when
calling envVarsResolver.getPollingEnvVars which means it's probably
throwing an exception. Where would I see that?
Thanks,
Greg
On Thursday, October 30, 2014 9:49:28 PM UTC-4, Greg Dickie wrote:
&
Hi,
I was using the script trigger plugin successfully however I think a
recent update broke it (or I did something stupid). Looking for a way to
debug it. Right now I get a very unhelpful:
Polling on master.
The expected script execution code is 0
[ERROR] - Polling error...
I grabbed the sou
Adding to my own post but it looks like this may be related
to JENKINS-13546.
On Wednesday, May 7, 2014 3:59:58 PM UTC-4, Greg Dickie wrote:
>
> Hi
>
> Ever since upgrading to 561 my remote build triggers are broken with:
>
> Building on master in workspace
> /var/
Hi
Ever since upgrading to 561 my remote build triggers are broken with:
Building on master in workspace /var/lib/jenkins/workspace/runner-automation
Triggering this remote job: automation
Not checking if the remote job automation is building.
This job is build #[32] on the remote server.
Trigg
:
> You should be able to poll without a workspace with stash using the "fast
> remote polling" option of the git plugin.
>
> /James
>
> > -Original Message-
> > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> > us...@googlegroups.com] On
mit notification anyway
>
>
> 2014-05-01 16:05 GMT+02:00 Greg Dickie :
>
>
> Hi Nicolas,
>
>
>I would like to understand the reason for that design.
> Maybe I'm using it incorrectly but it was doing
Hi Nicolas,
I would like to understand the reason for that design. Maybe I'm using
it incorrectly but it was doing what we needed. Why wouldn't you want SCM
polling, artifacts, etc.? Is the intention that we create build steps to
handle that stuff or is build flow not the right way to go fo
Hi,
We updated to the latest build flow without workspaces and all of the
change reporting seems to have broken. In addition builds are no longer
finding the latest git commit on branches. This is quite a setback for us.
What was the rational for those changes and is there an alternative
mec
