![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
github |
|
Created:
|
24/May/13 8:26 PM
|
|
Description:
|
If you have a slave node that goes offline when idle that holds the workspace of a build, any GitHub push automatically triggers a build with the message:
Started on May 24, 2013 8:15:43 PM
Workspace is offline.
Scheduling a new build to get a workspace. (nonexisting_workspace)
Done. Took 1 ms
Changes found
Two issues here:
- If the job is triggered by a "Test Hook" call from GitHub and the slave is offline, it was always make a build job even if the there isn't any changes.
- (unconfirmed but very likely) The job would build even if the branch it is supposed to build isn't the one that was updated because of the "nonexisting_workspace" error.
Thank you for your consideration.
I would like to propose that the status of the
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Joseph Lawson
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
