[JIRA] (JENKINS-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-36529 jenkins blocks on pipeline, won't terminate until restart Change By: Andrew Bayer Component/s: git-plugin Component/s: workflow-cps-plugin 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-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title Andrew Bayer commented on JENKINS-36529 Re: jenkins blocks on pipeline, won't terminate until restart This looks like some sort of race condition in the Git plugin. 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-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title Wilfried Goesgens commented on JENKINS-36529 Re: jenkins blocks on pipeline, won't terminate until restart I meanwhile worked around this using a python script deployed into my build containers: https://github.com/arangodb-helper/build-docker-containers/blob/master/scripts/copyFileLockedIfNewer.py used in a sh-step in this function: https://github.com/arangodb-helper/JenkinsScripts/blob/master/ci/Jenkinsfile#L74 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-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title Nathan Sullivan commented on JENKINS-36529 Re: jenkins blocks on pipeline, won't terminate until restart Getting the same thing here. Tried flushing the workspace, doesn't resolve it. Jenkins restarts seem to be the only thing to kick it over. 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-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title
Wilfried Goesgens updated an issue
Jenkins / JENKINS-36529
jenkins blocks on pipeline, won't terminate until restart
Change By:
Wilfried Goesgens
Tried to run this tiny script from an git scm pipeline: #!groovynode { git url: 'https://github.com/arangodb/arangodb.git' if (isUnix()) {echo 'Hello Unix'sh 'cmake . 'sh 'make' } else {echo 'hello else' }} Pressed twice 'play' by accident. stopped the upper run. This seemed to have voided my workspace. The checkout command below would block in all subsequent attepmts: It starts cloning into arangodb:[Pipeline] {[Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/arangodb/arangodb.git # timeout=10Fetching upstream changes from https://github.com/arangodb/arangodb.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/arangodb/arangodb.git +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10Checking out Revision ed80c3d2e88953e5054c1ea43e35eda39052f043 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ed80c3d2e88953e5054c1ea43e35eda39052f043 # timeout=10it then remains stuck. the git process vanishes from top/pstree. The complete pipeline will then remain in 'active' state, without a reaction to the X-button. Only restarting jenkins will get it out of this state. Flushing my workspace resolved this issue.
Add Comment
[JIRA] (JENKINS-36529) jenkins blocks on pipeline, won't terminate until restart
Title: Message Title
Wilfried Goesgens created an issue
Jenkins / JENKINS-36529
jenkins blocks on pipeline, won't terminate until restart
Issue Type:
New Feature
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2016/Jul/08 11:22 AM
Priority:
Minor
Reporter:
Wilfried Goesgens
Tried to run this tiny script from an git scm pipeline: #!groovy node { git url: 'https://github.com/arangodb/arangodb.git' if (isUnix()) { echo 'Hello Unix' sh 'cmake . ' sh 'make' } else { echo 'hello else' } } It starts cloning into arangodb: [Pipeline] { [Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/arangodb/arangodb.git # timeout=10 Fetching upstream changes from https://github.com/arangodb/arangodb.git > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/arangodb/arangodb.git +refs/heads/:refs/remotes/origin/ > git rev-parse refs/remotes/origin/master^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision ed80c3d2e88953e5054c1ea43e35eda39052f043 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f ed80c3d2e88953e5054c1ea43e35eda39052f043 # timeout=10 it then remains stuck. the git process vanishes from top/pstree. The complete pipeline will then remain in 'active' state, without a reaction to the X-button. Only restarting jenkins will get it out of this state.
