My build wasn't been triggered anymore as git poll kept failing to detect
the workspace after a job rename for a job assigned on my master.
Started on Sep 24, 2012 3:55:18 PM
No workspace is available, so can't check for updates.
Done.
Took 0 ms No changes
The associated code is in AbstractProject is:
if (scm.requiresWorkspaceForPolling()) {
// lock the workspace of the last build
FilePath ws=lb.getWorkspace();
if (workspaceOffline(lb)) {
// workspace offline. build now, or nothing will ever be
built
Label label = getAssignedLabel();
if (label != null && label.isSelfLabel()) {
// if the build is fixed on a node, then attempting a
build will do us
// no good. We should just wait for the slave to come
back.
listener.getLogger().println(Messages.AbstractProject_NoWorkspace());
return NO_CHANGES;
}
It looks like there is an assumption that the workspace is unavailable ->
the slave is offline.
This isn't the case. The job was renamed and the last build points to a non
existing workspace.
I worked around the problem by manually triggering the jobs.
Not sure if it was a bug somewhere else (e.g. job renaming) or normal
behavior. Should I file a bug somewhere on git polling ?
Jerome
