Robin
I think this is intended behaviour; the code in the workspace is used as
the basis for determining whether there are new changes to build; but a
new job with an empty workspace will always build on this first check.
As workspaces can be transient based on location (slaves for example)
this
I think the polling log for the build provides the real reason here:
Polling Log
View as plain text
This page captures the polling log that triggered this build.
Started on Jun 11, 2012 10:42:17 AM
No workspace is available, so can't check for updates.
Scheduling a new build to get a workspace.
** Attachment added: "/var/log/jenkins.log from that day"
https://bugs.launchpad.net/ubuntu/+source/jenkins/+bug/1011707/+attachment/3211731/+files/jenkins.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Hi Robin
Please could you extract this information from
/var/log/jenkins/jenkins.log as well - it may contain more information
as to why the build was triggered.
Thanks.
** Changed in: jenkins (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a mem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011707
Title:
Unnecessary rebuild triggered
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jenkins/+bug/101170
