[JIRA] [mansion-cloud-plugin] (JENKINS-26665) Complete lack of correct synchronization or concern for thread safety in mansion cloud plugin

Wed, 28 Jan 2015 06:22:30 -0800

Issue Type: Bug Bug
Assignee: Unassigned
Components: mansion-cloud-plugin
Created: 28/Jan/15 2:20 PM
Description:

So the mansion cloud plugin does not pay attention to locking when removing nodes. This can result in builds starting on a node that does not exist or a build being aborted while in progress as it gets removed. This will result in stack traces such as:

java.lang.IllegalStateException: no longer a configured node for 1f13542c
at hudson.model.AbstractBuild$AbstractBuildExecution.getCurrentNode(AbstractBuild.java:462)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
at hudson.model.Run.execute(Run.java:1745)
at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)


For correct behaviour look at some of the recent changes to the durable builds plugin within the retention strategy (or - if you are a bee - the closed source operations-center-cloud or nectar-vmware plugins of CloudBees... though this should just be additional examples of the changes pushed to the durable tasks plugin)
Project: Jenkins
Priority: Minor Minor
Reporter: stephenconnolly
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to