[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Oleg Nenashev updated JENKINS-39674 The fix has been resolved in 1.6.9 Jenkins / JENKINS-39674 Build name file path file gets locked by Jenkins process Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39674 Re: Build name file path file gets locked by Jenkins process Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/org/jenkinsci/plugins/buildnameupdater/BuildNameUpdater.java http://jenkins-ci.org/commit/build-name-setter-plugin/a2f70213e56f860dfb283178251d0b9fa7f8ecea Log: JENKINS-39674 - Prevent file descriptor leak in the Build Name Updater step Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39674 Re: Build name file path file gets locked by Jenkins process Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/org/jenkinsci/plugins/buildnameupdater/BuildNameUpdater.java http://jenkins-ci.org/commit/build-name-setter-plugin/f0cbc1eb4a93e1b07fcea813e7bda7cac5ae2764 Log: Merge pull request #18 from oleg-nenashev/JENKINS-39674 JENKINS-39674 - Prevent file descriptor leak in the Build Name Updater step Compare: https://github.com/jenkinsci/build-name-setter-plugin/compare/2074bde61078...f0cbc1eb4a93 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Oleg Nenashev updated JENKINS-39674 Jenkins / JENKINS-39674 Build name file path file gets locked by Jenkins process Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Oleg Nenashev started work on JENKINS-39674 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-39674 Build name file path file gets locked by Jenkins process Change By: Oleg Nenashev Assignee: Lev Mishin Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build. {{ The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. }} {{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true }}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build. {{ The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. }} {{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true}}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build.The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. {{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true}}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
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
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build.The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number.{{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true }}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
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
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Toby O'Sullivan commented on JENKINS-39674 Re: Build name file path file gets locked by Jenkins process Additional note: Cleaning the workspace also fails, and trying to delete the workspace on disk is not possible either as Windows reports the version.txt is locked by the java.exe process 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan created an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Issue Type:
Bug
Assignee:
Lev Mishin
Components:
build-name-setter-plugin
Created:
2016/Nov/11 3:43 PM
Environment:
Jenkins ver. 1.632 running on Windows 3012 R2 Build-name-setter v 1.5.1
Priority:
Minor
Reporter:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process. All other files are removed except "version.txt" in which we store a product version number specific to the build. The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. {{ version.txt #$ {BUILD_NUMBER} -$ {ibm.dv.git_branch} - true true true }} I have no concrete evidence or reproduction step I'm afraid, sorry about that. However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
