[JIRA] (JENKINS-36358) ws step does not lock the workspace
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-36358 ws step does not lock the workspace Change By: Vivek Pandey Labels: api lock triaged-2018-11 workspace Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-36358) ws step does not lock the workspace
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36358 ws step does not lock the workspace Change By: Jesse Glick Component/s: workflow-durable-task-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-36358) ws step does not lock the workspace
Title: Message Title Jesse Glick commented on JENKINS-36358 Re: ws step does not lock the workspace If implemented, could offer a Pipeline alternative to the Batch Task plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-36358) ws step does not lock the workspace
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-36358 ws step does not lock the workspace Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jun/30 2:22 PM Labels: workspace lock api Priority: Major Reporter: Jesse Glick Currently WorkspaceStepExecution just calls WorkspaceList.allocate. If there is some other build/thread using the designated workspace, it will simply append @2 etc. Better would be to have an option to call acquire, which would pause until the workspace is released and then acquire an exclusive lock. Unfortunately this would block the CPS VM thread and not survive restarts. Could force the exact path to be acquired only by setting up a background thread (with onResume) to block, or adding a core API to register a callback listener when any existing lease is released. Add Comment
