[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title
Douglas Royds updated an issue
Jenkins / JENKINS-25786
Renaming Job Causes a poisoned commitQueue
Change By:
Douglas Royds
Comment:
After renaming a job, we evidently wound up with a poisoned queue. scm-sync-configuration's attempts to delete the old job were failing:{noformat}[INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs' && 'git' 'rm' '-r' '--' 'reset-watchdog-test'[INFO] Working directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobsMar 07, 2016 11:09:27 AM hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchySEVERE: [deleteHierarchy] Problem during remove : The git command failed.{noformat}Status in ~/scm-sync-configuration/checkoutConfiguration was:{noformat}$ git status# On branch master# Your branch is up-to-date with 'origin/master'.## Changes to be committed:# (use "git reset HEAD ..." to unstage)## new file: jobs/reset-watchdog-test/config.xml#{noformat}The following actions failed:# Manually unstaged the offending (old) config.xml file and its directory# Deleted the local jobs/reset-watchdog-test directory and config.xml file# Committed and pushed.# Made a trivial edit in an unrelated job, and committed it (via the pop-up in the web-app)* scm-sync-configuration reported an error* The (old) config.xml file had reappeared, and was staged.Another approach also failed:# Manually committed the (staged) config.xml file# Made a trivial edit in an unrelated job, and committed it (via the pop-up in the web-app)* scm-sync-configuration reported an errorExamining the tomcat log, scm-sync-configuration was trying to run the following command:{noformat}[INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration' && 'git' 'add' '--' 'jobs'[INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration' && 'git' 'add' '--' 'jobs/reset-watchdog-test'[INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration' && 'git' 'add' '--' 'jobs/reset-watchdog-test/config.xml'[INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration' && 'git' 'rev-parse' '--show-toplevel'[INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration' && 'git' 'status' '--porcelain' '.'[INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs' && 'git' 'rm' '-r' '--' 'reset-watchdog-test'{noformat}When I ran the git rm -r command myself from the command-line, with the config.xml file staged, git failed:{noformat}error: the following file has changes staged in the index:jobs/reset-watchdog-test/config.xml(use --cached to keep the file, or -f to force removal){noformat}The workaround that avoided having to restart Jenkins just to un-poison the queue (this is a very busy little box) was to manually commit the rogue config.xml file, so that the git rm -r could work. With the file already staged:{noformat}$ git commit jobs/reset-watchdog-test/config.xml -m"Fake commit"[master d348b30] Fake commit 1 file changed, 103 insertions(+) create mode 100644 jobs/reset-watchdog-test/config.xml{noformat}I returned to the web-app and made a trivial commit, and the problem was gone. scm-sync-configuration cheerfully deleted
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Douglas Royds commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue After renaming a job, we evidently wound up with a poisoned queue. scm-sync-configuration's attempts to delete the old job were failing: [INFO] Executing: /bin/sh -c cd '/var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs' && 'git' 'rm' '-r' '--' 'reset-watchdog-test' [INFO] Working directory: /var/lib/jenkins/scm-sync-configuration/checkoutConfiguration/jobs Mar 07, 2016 11:09:27 AM hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy SEVERE: [deleteHierarchy] Problem during remove : The git command failed. Status in ~/scm-sync-configuration/checkoutConfiguration was: $ git status # On branch master # Your branch is up-to-date with 'origin/master'. # # Changes to be committed: # (use "git reset HEAD ..." to unstage) # # new file: jobs/reset-watchdog-test/config.xml # The following actions failed: Manually unstaged the offending (old) config.xml file and its directory Deleted the local jobs/reset-watchdog-test directory and config.xml file Committed and pushed. Made a trivial edit in an unrelated job, and committed it (via the pop-up in the web-app) scm-sync-configuration reported an error The (old) config.xml file had reappeared, and was staged. Another approach also failed: Manually committed the (staged) config.xml file Made a trivial edit in an unrelated job, and committed it (via the pop-up in the web-app) scm-sync-configuration reported an error
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title David Cullen edited a comment on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue Hello, [~cobexer], when I have this problem, there are no changes that need to be committed. If I run "git status" it tells me that I am behind the remote by N commits. The plugin stops pushing to the remote after a job is renamed and nothing I do (besides the steps I listed) fixes it. I am just glad that I figured out a way to recover the GIT history. Before I found out how to merge two repositories, I was losing the commit history when I deleted the repository from GitLab. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title David Cullen commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue Hello, Christoph Obexer, when I have this problem, there are not changes that need to be committed. If I run "git status" it tells me that I am behind the remote by N commits. The plugin stops pushing to the remote after a job is renamed and nothing I do (besides the steps I listed) fixes it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title David Cullen edited a comment on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue Hello, [~cobexer], when I have this problem, there are not no changes that need to be committed. If I run "git status" it tells me that I am behind the remote by N commits. The plugin stops pushing to the remote after a job is renamed and nothing I do (besides the steps I listed) fixes it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Christoph Obexer commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue David Cullen Have you tried to just git commit the changes that are already in the scm-sync-configuration/checkoutConfiguration directory? modifying jobs with spaces always causes this for me and just committing manually fixes it for me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title David Cullen commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue I use Gitlab, and I have to fix this by Uninstalling the "SCM Sync Configuration Plugin" Restarting Jenkins sudo su - tomcat7 pushd .jenkins rm -fr scm-sync-configuration* Restarting Jenkins Renaming the repository on GitLab Creating a new repository on GitLab with the original name Re-installing the "SCM Sync Configuration Plugin" Configure the "SCM Sync Configuration Plugin" pushd scm-sync-configuration/checkoutConfiguration git remote add scm-sync-configuration-old git fetch scm-sync-configuration-old git merge scm-sync-configuration-old/master git remote remove scm-sync-configuration-old git branch --unset-upstream There is a mix of GitLab operations and shell commands and obviously I am using tomcat to run Jenkins. However, this might work for someone else, so I am putting the information here. Doing all of that preserves the history that I would normally lose. I wish there was a way to use Jenkins security to only allow copying repositories and block renaming.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Trevor Baker reopened an issue Jenkins / JENKINS-25786 Renaming Job Causes a poisoned commitQueue Change By: Trevor Baker Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Trevor Baker commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue We're still having issues though the job to be renamed contains a space in the name, which is issue JENKINS-24686. JENKINS-24686 is marked fixed, though I am still seeing that same stacktrace on 0.0.9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in 0.0.9 Jenkins / JENKINS-25786 Renaming Job Causes a poisoned commitQueue Change By: Craig Rodrigues Status: Open Resolved Assignee: Frédéric Camblor Craig Rodrigues Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Stefan Schäfer commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue lol Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title
Trevor Baker edited a comment on JENKINS-25786
Re: Renaming Job Causes a poisoned commitQueue
When this happens I see the old named job's config.xml committed properly though the add of the newly named file doesn't happen. You end with with the renamed file and path untracked in scm-sync-configuration/checkoutConfigurationThis is how I fix it: ``` {code:java} ssh jenkinssudo su jenkins -s /bin/bashcd ~/scm-sync-configuration/checkoutConfiguration/git status # see untracked filesgit add -agit commit -a -m “fix this busted stuff”git push origin master# all good ``` {code} Then restart Jenkins.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Title: Message Title Trevor Baker commented on JENKINS-25786 Re: Renaming Job Causes a poisoned commitQueue When this happens I see the old named job's config.xml committed properly though the add of the newly named file doesn't happen. You end with with the renamed file and path untracked in scm-sync-configuration/checkoutConfiguration This is how I fix it: ``` ssh jenkins sudo su jenkins -s /bin/bash cd ~/scm-sync-configuration/checkoutConfiguration/ git status # see untracked files git add -a git commit -a -m “fix this busted stuff” git push origin master all good ``` Then restart Jenkins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Kenneth Baltrinic updated JENKINS-25786 Renaming Job Causes a poisoned commitQueue Updating the priority of this because it is causing backups to fail across our enterprise. Change By: Kenneth Baltrinic (13/Feb/15 1:45 PM) Priority: Minor Critical 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.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Kenneth Baltrinic edited a comment on JENKINS-25786 Renaming Job Causes a poisoned commitQueue Updating the priority of this because it is causing backups to fail across our enterprise. Both renaming jobs and deleting them (JENKINS-26652) result in a poisoned queue. Likely other errors also lead to this. 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.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
thedug commented on JENKINS-25786 Renaming Job Causes a poisoned commitQueue +1 I also noticed that the plugin is only committing changes when I save jenkins settings not when saving changes to projects (I don't even get the commit message popup). I'm not sure when that happened but I have a suspicion that it was related to this. 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.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Daniel Beck commented on JENKINS-25786 Renaming Job Causes a poisoned commitQueue Updating the priority of this because it is causing backups to fail across our enterprise. Workaround: Disable this plugin. 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.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
thedug commented on JENKINS-25786 Renaming Job Causes a poisoned commitQueue I've run into the same thing. I usually just go into the checkOutConfiguration and try to make it match. Sometimes it seems to get into a state where there are recursive references, I usually delete those extra folders. Commit and Push to git. Then restart jenkins. 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.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Harry Weppner commented on JENKINS-25786 Renaming Job Causes a poisoned commitQueue Are there instructions how to "clean up the checkoutConfiguration directory"? Thanks! 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.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-25786) Renaming Job Causes a poisoned commitQueue
Kenneth Baltrinic created JENKINS-25786 Renaming Job Causes a poisoned commitQueue Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 26/Nov/14 2:29 AM Description: Renaming a job causes a commit to be added to the scm-sync plug-in's internal commit queue (see ScmSyncConfigurationBusiness.java) that fails due to the issue documented in JENKINS-15128 - Renaming job doesn't work with Git. Thereafter, even if one cleans up the checkoutConfiguration directory and manually syncs everything up, it become necessary to restart Jenkins because the failed commit poisons the queue. The remaining issue with 15128 (not calling git rm with the recursive flag) means the commit can never succeed. All subsequent configuration changes get stuck behind it. There needs to be a way to reset the queue queue w/o restarting Jenkins. Environment: Jenkins v 1.552 scm-sync v 0.0.8 Project: Jenkins Priority: Minor Reporter: Kenneth Baltrinic 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.
