|
||||||||
|
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/d/optout.
We were able to solve this by checking the "Build needs workspace" - checkbox. That way the buildflow is created as a AbstractRunner instead of RunExecution (we checked the code).
Claim-plugin works if buildflow is AbstractRunner, but this is deprecated.
We even tried to revert from RunExecution to ActractRunner, and then all jobs works with the claim-plugin. Not sure if Claim-plugin should be changed or the BuildFlow update to be visible for the Claim-plugin.
class FlowRun
protected class FlyweightTaskRunnerImpl extends RunExecution //Not working with claim
protected class BuildWithWorkspaceRunnerImpl extends AbstractRunner //Works with claim, this is used when "Build needs workspace" is checked.