[JIRA] [scm-sync-configuration-plugin] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0
Title: Message Title kennabec walp commented on JENKINS-21640 Re: scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0 Is this actually fixed? I still see the same issues with 0.0.9 and Subversion 2.5.5 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0
Title: Message Title Craig Rodrigues closed an issue as Fixed Fixed in 0.0.9 Jenkins / JENKINS-21640 scm-sync-configuration plugin doesn't work anymore with Subversion Plugin >=2.0 Change By: Craig Rodrigues Status: Open Closed 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Title: Message Title Alan Birtles commented on JENKINS-21640 Re: scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0 and broken again in 1.613, svn 2.5 and scm 0.0.8 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Alan Birtles commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 all working for me as well with jeninks 1.607, svn 2.5 and scm 0.0.8 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Alan Birtles
edited a comment on JENKINS-21640
scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0
I've found a temporary workaround by running the following script as a daily job:
cp ${JENKINS_HOME}/*.xml ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/
rsync -avm --include='config.xml' -f 'hide,! */' ${JENKINS_HOME}/jobs/ ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
svn add --force ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/*
if svn status ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ | grep '^[AMCDG]' ; then
svn ci ${JENKINS_HOME}/scm-sync-configuration/checkoutConfiguration/ -m ""
else
echo "No changes found"
fi
It's not quite as good as the scm sync but it does the job
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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Dan Rough commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 @Cameron, @Arun 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Arun Thomas commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 @Dan Rough: Yes, I am able to rename without errors with the current plugins. I remember having issues when renaming jobs with the older versions. 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Dan Rough commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 @Arun Thomas are deletes and modifications working for you? The last time I attempted to use this plugin I encountered a problem if I renamed items - the sync with Git would fail. Have you come across 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Cameron commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 @Dan Rough: We had the problem with renaming jobs too (with the older version of Jenkins). I guess it's a known bug that just never got fixed. We remove the SCM plugin's subversion URL and then put it back as a workaround to make the plugin happy again. 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Roel Harbers commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 So, with this blocker ticket being open for more than a year, I guess we can conclude that this is not going to work anytime soon? What would be the consequences of using an ancient version of the Subversion plugin? (2.0) 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Arun Thomas commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 SCM Sync plugin is working for me. Jenkins: 1.599 Sub-version plugin: 2.5 SCM Sync Configuration plugin: 0.0.8 Environment: Windows Server 2008 Could this have been resolved? Has anyone else tried the latest plugins? 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-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Alan Birtles
commented on JENKINS-21640
scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0
I've found a temporary workaround by running the following script as a daily job:
cp ${JENKINS_HOME}/*.xml ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/
rsync -avm --include='config.xml' -f 'hide,! */' ${JENKINS_HOME}/jobs/ ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
svn add --force ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/
if svn status ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/ | grep '^[AMCDG]' ; then
svn ci ${JENKINS_HOME}/scm-sync-configuration/checkoutConfgiguration/jobs/ -m ""
else
echo "No changes found"
fi
It's not quite as good as the scm sync but it does the job
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.
