[JIRA] [scm-sync-configuration-plugin] (JENKINS-28391) Allow excluding files from Manual synchronization includes
Title: Message Title Frdric Camblor commented on JENKINS-28391 Re: Allow excluding files from Manual synchronization includes Duplicate of JENKINS-18187 A more generic solution has been proposed in JENKINS-19659. What do you think about it ? Are you ok to close current issue ? 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-28391) Allow excluding files from Manual synchronization includes
Title: Message Title Frdric Camblor commented on JENKINS-28391 Re: Allow excluding files from Manual synchronization includes Fine, thanks 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-27750) SSH Credential's from Jenkins credential-store are not used.
Frédéric Camblor closed JENKINS-27750 as Duplicate SSH Credentials from Jenkins credential-store are not used. Dupe of JENKINS-18129 Change By: Frédéric Camblor (06/Apr/15 10:12 AM) Status: Open Closed Resolution: Duplicate 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-27591) Improve performance of initial scan by narrowing the job config pattern
Frédéric Camblor commented on JENKINS-27591 Improve performance of initial scan by narrowing the job config pattern Agree with your assumptions, you're right 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-27591) Improve performance of initial scan by narrowing the job config pattern
Frédéric Camblor commented on JENKINS-27591 Improve performance of initial scan by narrowing the job config pattern This change was introduced by @ndeloof for Cloudbees folder plugin (see this commit) Wondering what to do... 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-27591) Improve performance of initial scan by narrowing the job config pattern
Frédéric Camblor updated JENKINS-27591 Improve performance of initial scan by narrowing the job config pattern Change By: Frédéric Camblor (25/Mar/15 3:42 PM) Priority: Blocker Major 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-27519) NullPointerException on save config with svn+ssh connection
Frédéric Camblor commented on JENKINS-27519 NullPointerException on save config with svn+ssh connection Don't think it is related to scm-sync-config plugin It appears in the stack because it is a plugin filter 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-25454) Jobs with spaces in name lead to crash in plugin
Frédéric Camblor closed JENKINS-25454 as Duplicate Jobs with spaces in name lead to crash in plugin Dupe Change By: Frédéric Camblor (05/Nov/14 4:02 PM) Status: Open Closed Resolution: Duplicate 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] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git mmm.. I didn't tested it against file hierarchy (to test, I only settled simple freestyle job, thus not having any subdirectories) There must be another issue here, could you file another issue about this please ? 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] (JENKINS-15898) Subversion back-end cannot handle renaming of jobs
Frédéric Camblor commented on JENKINS-15898 Subversion back-end cannot handle renaming of jobs FYI, JENKINS-15128 was fixed in 0.0.8 Could someone test this version (once it will have poped in jenkins plugin repos) to see if scm-api update from 1.6 to 1.9.1 wouldn't fix the issue for svn ? 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] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor resolved JENKINS-15128 as Fixed Renaming job doesnt work with Git fixed in v0.0.8 Change By: Frédéric Camblor (24/Aug/14 9:07 AM) Status: Open Resolved Assignee: FrédéricCamblor Resolution: Fixed 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] (JENKINS-19229) Git repo: fails when we delete the jobs.
Frédéric Camblor resolved JENKINS-19229 as Duplicate Git repo: fails when we delete the jobs. FYI, JENKINS-15128 was fixed in 0.0.8 Change By: Frédéric Camblor (24/Aug/14 9:20 AM) Status: Open Resolved Resolution: Duplicate 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] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor resolved JENKINS-22820 as Fixed Changes are not commited when using a recent git client Thanks @rogerhu for the PR, merged ! It will be part of v0.0.8 (release in progress) Change By: Frédéric Camblor (24/Aug/14 8:58 AM) Status: Open Resolved Resolution: Fixed 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] (JENKINS-24339) SCM sync Configuration plugin seems to wrongly expect all files to be under JENKINS_HOME
Frédéric Camblor closed JENKINS-24339 as Duplicate SCM sync Configuration plugin seems to wrongly expect all files to be under JENKINS_HOME dupe of JENKINS-13593 Change By: Frédéric Camblor (20/Aug/14 12:15 PM) Status: Open Closed Resolution: Duplicate 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] (JENKINS-24226) use credentials-plugin to define SCM credentials
Frédéric Camblor closed JENKINS-24226 as Duplicate use credentials-plugin to define SCM credentials dup for JENKINS-21640 Change By: Frédéric Camblor (13/Aug/14 8:48 AM) Status: Open Closed Resolution: Duplicate 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] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client ok, since it was quite a long time (sorry for the late reply ), I would have thought you tested with a version before 1.9 (which seems to contain a fix for the --porcelain command line) 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] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client I'm not speaking about maven-release-plugin, but about the direct pom dependency 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] (JENKINS-22820) Changes are not commited when using a recent git client
Frédéric Camblor commented on JENKINS-22820 Changes are not commited when using a recent git client Hi there ! It seems Emmanuel was right. First, there seems to have a "simple" workaround described here (setting LANG to en_US.UTF-8) @Brice did you try to use maven-scm-provider-gitexe v1.9 (or above) as stated here ? If this confirm the resolution, I'll align on this version of the 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] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin =2.0
Frédéric Camblor updated JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin =2.0 Change By: Frédéric Camblor (24/Jul/14 10:46 AM) Summary: scm-sync-configurationplugindoesntworkanymorewithSubversionPlugin = 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] (JENKINS-23806) Managed script files are not included in scm config
Frédéric Camblor closed JENKINS-23806 as Wont Fix Managed script files are not included in scm config The plugin cannot be aware of every files handled by every possible jenkins plugins. Use manual includes in that case (prior to this, you will need to locate which files are concerned in order to provide manual synchronization includes for them) Change By: Frédéric Camblor (17/Jul/14 7:47 AM) Status: Open Closed Resolution: WontFix 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] (JENKINS-23799) SCM Sync configuration plugin synchronizes tar.gz files ?!
Frédéric Camblor closed JENKINS-23799 as Duplicate SCM Sync configuration plugin synchronizes tar.gz files ?! I prefer to close it for the moment. But don't hesitate to re-open it if you see the issue is still present in 0.0.7.5 Change By: Frédéric Camblor (17/Jul/14 10:55 AM) Status: Open Closed Resolution: Duplicate 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] (JENKINS-14847) Apply button not taken into account
Frédéric Camblor commented on JENKINS-14847 Apply button not taken into account Disagree, these are different topics (apply button implies some design changes to current scm-sync-config behaviour, mainly due to the XHR form submission) 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] [global-build-stats] (JENKINS-23225) RFE - Add support for viewing statistics per folder
Frédéric Camblor commented on JENKINS-23225 RFE - Add support for viewing statistics per folder Agree 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] (JENKINS-22951) SCM Sync no longer working as of last few versions.
Frédéric Camblor closed JENKINS-22951 as Duplicate SCM Sync no longer working as of last few versions. Change By: Frédéric Camblor (21/May/14 8:54 PM) Status: Open Closed Resolution: Duplicate 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] (JENKINS-21827) Error with SCM-syn-configuration
Frédéric Camblor commented on JENKINS-21827 Error with SCM-syn-configuration Which version of svn plugin do you use ? There seems to be a problem with svn 2.0 (and greater) 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] (JENKINS-21827) Error with SCM-syn-configuration
Frédéric Camblor closed JENKINS-21827 as Duplicate Error with SCM-syn-configuration dupe of JENKINS-21640 Change By: Frédéric Camblor (20/May/14 4:14 PM) Status: Reopened Closed Resolution: Duplicate 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] (JENKINS-21827) Error with SCM-syn-configuration
Frédéric Camblor commented on JENKINS-21827 Error with SCM-syn-configuration I think you should track JENKINS-21640 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] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0
Frédéric Camblor commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0 Downgrade to subversion plugin 2.0 But I don't know if the downgrade will play well with your upgraded config.xml files, make tests before downgrading. 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] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0
Frédéric Camblor commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0 Yup, this plugin is a good alternative 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] (JENKINS-22540) Jenkins config files are not tracked
Frédéric Camblor commented on JENKINS-22540 Jenkins config files are not tracked Hi, There is a plan to de-activate the default /hudson*.xml file pattern from default includes. I think the /jenkins*.xml should follow the same rule. BTW, before this is implemented, you can add your own manual includes in the scm-sync-configuration section. 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] (JENKINS-19984) Groovy Postbuild Plugin does not like Jenkins Option: Build Record Root Directory
Frédéric Camblor commented on JENKINS-19984 Groovy Postbuild Plugin does not like Jenkins Option: Build Record Root Directory Seems a dupe of JENKINS-13593 isn't it ? 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] [nodejs] (JENKINS-22102) NodeJS plugin does not remember the saved NodeJS Installation
Frédéric Camblor updated JENKINS-22102 NodeJS plugin does not remember the saved NodeJS Installation Change By: Frédéric Camblor (04/Apr/14 1:42 PM) Priority: Minor Major 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] [nodejs] (JENKINS-22103) NodeJS buildstep succeeds, although installation failed
Frédéric Camblor commented on JENKINS-22103 NodeJS buildstep succeeds, although installation failed I agree with your assumption. But I'm wondering if I can do anything about this : I'm relying on a common "XXX Installations" layer which seems to behave like this by default. I'll try to see if I can change this default behaviour 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] (JENKINS-22365) Cannot install latest version of scm-sync-configuration plugin
Frédéric Camblor commented on JENKINS-22365 Cannot install latest version of scm-sync-configuration plugin Don't know where this 0.0.7.4 comes from. I didn't released it, and there doesn't seem to be any commit/tag on github about 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] [global-build-stats] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart
Frédéric Camblor commented on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart @Jason @Jakub : thanks for the details, it will help for sure. Unfortunately I still can't succeed in reproducing the issue (but I'm on a more recent Jenkins, 1.532.2) @All could you try the plugin on the LTS version just after your version ? For Maxfield who is on 1.484, this would be 1.509.4 For Jason, who is on 1.455, this would be 1.466.2 Non LTS can be really buggy sometimes, so I prefer to be sure we're not hitting some core (xstream) bug resolved in a more recent version of 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] (JENKINS-22076) SCM Sync Configuration crashes after enter repository URL
Frédéric Camblor commented on JENKINS-22076 SCM Sync Configuration crashes after enter repository URL What is your subversion plugin version ? 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] (JENKINS-22076) SCM Sync Configuration crashes after enter repository URL
Frédéric Camblor edited a comment on JENKINS-22076 SCM Sync Configuration crashes after enter repository URL Ok I think the switch to credentials plugins in subversion-plugin 2.0 is the culprit. I won't be able to provide any fix in the short term because it implies a big refactoring. More input about this topic in JENKINS-18129 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] (JENKINS-22076) SCM Sync Configuration crashes after enter repository URL
Frédéric Camblor edited a comment on JENKINS-22076 SCM Sync Configuration crashes after enter repository URL Ok I think the switch to credentials plugins in 2.0 is the culprit. I won't be able to provide any fix in the short term because it implies a big refactoring. More input about this topic in JENKINS-18129 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] (JENKINS-22040) SCM sync commits its own checkout
Frédéric Camblor commented on JENKINS-22040 SCM sync commits its own checkout Wow you're perfectly right. But in practice, I never had these files checked in, but I don't know why it's working on initial check in Is checkoutConfiguration/ file tree checked in on your repo ? 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-22040) SCM sync commits its own checkout
Frédéric Camblor commented on JENKINS-22040 SCM sync commits its own checkout Note that these files will be checked in rarely (only on initial checkin) because no jenkins model change is related to these files But I agree with you for the exclusion 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git Another workaround is to avoid renaming jobs, and prefer create new job by copying the old one, then remove the old job. Drawbacks for this solution : Build history is lost I totally agree this is not ideal, especially on large user codebase where we cannot keep an eye on everyone's job config But this is the only I can provide now. Fixing this issue would imply a big refactor on the way the plugin uses the scm abstractions (see my previous comments), and this is not something I have time to do nowadays. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21827) Error with SCM-syn-configuration
Frédéric Camblor closed JENKINS-21827 as Wont Fix Error with SCM-syn-configuration I can't support every jenkins version in the wild. Will only support LTS versions. Could you try with latest (1.532.2) and see if you can reproduce your problem ? Change By: Frédéric Camblor (17/Feb/14 9:12 AM) Status: Open Closed Resolution: WontFix 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21807) SCM Sync Configuration crashes after enter repository URL
Frédéric Camblor resolved JENKINS-21807 as Duplicate SCM Sync Configuration crashes after enter repository URL dupe of JENKINS-14847 Change By: Frédéric Camblor (14/Feb/14 9:21 AM) Status: Open Resolved Resolution: Duplicate 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/groups/opt_out.
[JIRA] [nodejs] (JENKINS-21726) Nodejs path not set correctly when running on Windows master, linux slave
Frédéric Camblor resolved JENKINS-21726 as Fixed Nodejs path not set correctly when running on Windows master, linux slave fixed in 0.2.1 Change By: Frédéric Camblor (10/Feb/14 8:48 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0
Frédéric Camblor commented on JENKINS-21640 scm-sync-configuration plugin doesnt work anymore with Subversion Plugin 2.0 Arg ... as if it weren't already complicated enough Seems like maintaining compatibility will be a pain. Note that I linked this issue with JENKINS-18124 about scm modularization. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18036) scm-sync plugin ends up in commit-conflicts and eventually eats most of available CPU time
Frédéric Camblor commented on JENKINS-18036 scm-sync plugin ends up in commit-conflicts and eventually eats most of available CPU time Have you tried to run `svn cleanup` in JENKINS_HOME/scm-sync-configuration/checkoutConfiguration/ folder ? 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git Hi, Workaround for job renames is : Stop Jenkins Manually `git mv` directories in the checkoutConfiguration/ directory, commit change, then push the commit to your repository Restart Jenkins In last resort, you can switch in the global config page : Git SCM = No SCM + save = Git SCM + save This will result in : Resetting checkoutConfiguration/ content (changing scm resets the directory) Performing a new "initial sync" with the repository, that is to say : Clone repo into checkoutConfiguration Add folders located into your JENKINS_HOME/ and not present into checkoutConfiguration/ to the repo Initial sync has a drawback : if you have checkoutConfiguration/foo and JENKINS_HOME/foo doesn't exist, foo won't be removed from your repository (I prefer not to remove such files due to "reload files from repo" feature) 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21107) can't commit / or check out from local git repository (local filesystem)
Frédéric Camblor commented on JENKINS-21107 cant commit / or check out from local git repository (local filesystem) Instead of `git init` please try `git init --bare` when initializing your repository 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21107) can't commit / or check out from local git repository (local filesystem)
Frédéric Camblor commented on JENKINS-21107 cant commit / or check out from local git repository (local filesystem) You're welcome 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Frédéric Camblor commented on JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? This reminds me of JENKINS-17545 and a bug in the scan() method used, and which was fixed prior to version 0.0.7.2 Which version of the plugin are you using ? 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21096) scm-sync-configuration: Store artifacts in git, is this really intended?
Frédéric Camblor commented on JENKINS-21096 scm-sync-configuration: Store artifacts in git, is this really intended? Great ! 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-19659) Allow to deactivate bundled scm sync config strategies
Frédéric Camblor updated JENKINS-19659 Allow to deactivate bundled scm sync config strategies Change By: Frédéric Camblor (20/Nov/13 8:14 AM) Description: AfterdiscussiononJENKINS-18187,itappearsitwouldbeanicefeaturetobeingabletodisable[defaultbundledstrategies| i http: / /github.com/jenkinsci/ scm-sync-configuration-plugin/tree/master/src/main/java/hudson/plugins/scm_sync_configuration/strategies/impl]atruntime(onjenkinsglobalconfigpage)Itwouldallowabettertuningofthescm-sync-configbehaviour. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-19660) Allow to commit SYSTEM-modified files only periodically
Frédéric Camblor commented on JENKINS-19660 Allow to commit SYSTEM-modified files only periodically @clint In your case, I think you could be interested in JENKINS-19659 too Including hudson*.xml files by default is maybe a bad idea as well. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-20626) SCM-sync-configuration plugin: make root directory in repository configurable
Frédéric Camblor commented on JENKINS-20626 SCM-sync-configuration plugin: make root directory in repository configurable I don't think separate implementation for each SCM is necessary. Providing a new relative path at scm-sync-configuration config section (which then could be used in ScmSyncConfigBusiness. getCheckoutScmDirectoryAbsolutePath()) would be sufficient. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor commented on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing Ok my bad, didn't understood you were talking about specific file "chunks" avoiding a new commit. To be honest, what you ask seems really complicated to implement (not triggering a commit based on the chunk modification, in a generic way). But JENKINS-19660 could bring a part of the answer : this +/-1 are SYSTEM modifications, so we shouldn't take them into account right now. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18875) st:bind seems to include json2.js, but not everytime
Frédéric Camblor closed JENKINS-18875 as Wont Fix st:bind seems to include json2.js, but not everytime Thx this is what I was expecting, closing the issue. Do you know where I could see the available (stapler) jelly tags documentations ? Because on http://stapler.kohsuke.org/jelly-taglib-ref.html there wasn't any reference for `bind` tag Change By: Frédéric Camblor (23/Jul/13 7:22 AM) Status: Open Closed Resolution: WontFix 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor updated JENKINS-18867 Wrong binding for the remove logs button Attached a dedicated hpi which should fix the problem. Could you install it and see if it solves your problem ? Change By: Frédéric Camblor (23/Jul/13 7:26 AM) Attachment: scm-sync-configuration-JENKINS-18867.hpi 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor edited a comment on JENKINS-18867 Wrong binding for the remove logs button Attached a dedicated hpi which should fix the problem. Could you install it and see if it solves your problem (I cannot reproduce the problem on my instance) ? 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor resolved JENKINS-18867 as Fixed Wrong binding for the remove logs button Change By: Frédéric Camblor (23/Jul/13 7:43 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor commented on JENKINS-18867 Wrong binding for the remove logs button Yep, there is a "Jquery plugin" which is generally pulled by another plugin, and which should alter the st:bind behaviour. You have it and I don't Will try to release a new version 0.0.7.3 when I'll have a little time. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor commented on JENKINS-18867 Wrong binding for the remove logs button Could your please provide : Your jenkins version Your browser version 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/groups/opt_out.
[JIRA] [core] (JENKINS-18875) st:bind seems to include json2.js, but not everytime
Frédéric Camblor
created JENKINS-18875
st:bind seems to include json2.js, but not everytime
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
22/Jul/13 4:33 PM
Description:
When installing SCM-Sync-Configuration plugin v0.0.7.2 on 1.523, it seems like this line of code :
var plugin = st:bind value="${it}"/;
is sometimes (depending on Jenkins installations) generating a strange output in the HTML :
var plugin = script src='' type='text/_javascript_'/scriptmakeStaplerProxy('/jenkins/$stapler/bound/47f87312-880f-40fc-9a12-0a75149deedc','xx',['purgeScmSyncConfigLogs']);
Whereas in 1.509.2, I have this generated output :
var plugin = makeStaplerProxy('/$stapler/bound/some-token','another token',['purgeScmSyncConfigLogs']);
I personnally don't reproduce it on a fresh 1.523 install, but Björn Pedersen is reproducing it on its instance.
Is there something bad :
In my code (I shouldn't affect the call to st:bind to a js variable because it could potentially has to include necessary third party js files like json2.js)
= if this is the case, is there a workaround to proxify my plugin instance on the JS clientside world ? (other than having to do stuff by hand by sending manual Ajax calls to the server side)
In Björn Pedersen's installation, or Jenkins core ?
Environment:
Jenkins 1.523
Project:
Jenkins
Priority:
Major
Reporter:
Frédéric Camblor
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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor commented on JENKINS-18867 Wrong binding for the remove logs button I just raised JENKINS-18875 because it doesn't seem to be related to the plugin You can track this issue to have feedback about your problem 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor
commented on JENKINS-18867
Wrong binding for the remove logs button
I just download 1.523 and cannot reproduce your issue
In the html page, I have :
function removeLog() {
var plugin = makeStaplerProxy('/$stapler/bound/445063c5-e7f0-4900-bf56-666d02720240','bc2fe9c2-6963-46ba-bf58-6dbcd40eb78d',['purgeScmSyncConfigLogs']);
plugin.purgeScmSyncConfigLogs();
alert("SCM Sync Config errors purged ! You can refresh the page.");
}
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/groups/opt_out.
[JIRA] [core] (JENKINS-18875) st:bind seems to include json2.js, but not everytime
Frédéric Camblor
updated JENKINS-18875
st:bind seems to include json2.js, but not everytime
Change By:
Frédéric Camblor
(22/Jul/13 4:39 PM)
Description:
WheninstallingSCM-Sync-Configurationpluginv0.0.7.2on1.523,itseemslike[thislineofcode|https://github.com/jenkinsci/scm-sync-configuration-plugin/blob/master/src/main/resources/hudson/plugins/scm_sync_configuration/extensions/ScmSyncConfigurationPageDecorator/footer.jelly#L64]:{code}varplugin=st:bindvalue=${it}/;{code}issometimes(dependingonJenkinsinstallations)generatingastrangeoutputintheHTML:{code}varplugin=scriptsrc="">{code}Whereasin1.509.2,Ihavethisgeneratedoutput:{code}varplugin=makeStaplerProxy(/$stapler/bound/some-token,anothertoken,[purgeScmSyncConfigLogs]);{code}Ipersonnallydontreproduceitonafresh1.523install,butBjörnPedersenisreproducingitonitsinstance.Istheresomethingbad:-Inmycode(Ishouldntaffectthecalltost:bindtoajsvariablebecauseitcould_potentially_hastoincludenecessarythirdpartyjsfileslikejson2.js)=ifthisisthecase,isthereaworkaroundtoproxifymyplugininstanceontheJSclientsideworld?(otherthanhavingtodostuffbyhandbysending_manual_Ajaxcallstotheserverside)-InBjörnPedersensinstallation,orJenkinscore?
Sidenote:Seemslikethesourceoftheproblemislocatedin[thiscommit|https://github.com/stapler/stapler/commit/48cdf0f3242c6a79bb398e9115c0db7526c42a50#L4R74]whichloadsjson2.jsifitisntalreadyloaded.
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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor
edited a comment on JENKINS-18867
Wrong binding for the remove logs button
I just downloaded 1.523 and cannot reproduce your issue
In the html page, I have :
function removeLog() {
var plugin = makeStaplerProxy('/$stapler/bound/445063c5-e7f0-4900-bf56-666d02720240','bc2fe9c2-6963-46ba-bf58-6dbcd40eb78d',['purgeScmSyncConfigLogs']);
plugin.purgeScmSyncConfigLogs();
alert("SCM Sync Config errors purged ! You can refresh the page.");
}
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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor updated JENKINS-18867 Wrong binding for the remove logs button Change By: Frédéric Camblor (22/Jul/13 2:49 PM) Environment: scm-sync-configurationv0.0.7.2 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18867) Wrong binding for the remove logs button
Frédéric Camblor edited a comment on JENKINS-18867 Wrong binding for the remove logs button I don't reproduce your issue on 1.509.2 (latest LTS) either. I just raised JENKINS-18875 because it doesn't seem to be related to the plugin You can track this issue to have feedback about your problem 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Frédéric Camblor resolved JENKINS-15734 as Fixed NullPointerException in ScmSyncConfigurationPlugin.getInstance Should be fixed in upcoming 0.0.7.2 Change By: Frédéric Camblor (19/Jul/13 7:28 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Frédéric Camblor resolved JENKINS-18715 as Fixed scandir being triggered by FingerPrint.save ok great PR will be available in upcoming 0.0.7.2 I'll try to release today Change By: Frédéric Camblor (19/Jul/13 7:30 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-17201) SCM Sync page does not match current version (options explanations missing)
Frédéric Camblor resolved JENKINS-17201 as Fixed SCM Sync page does not match current version (options explanations missing) Fixed, but don't hesitate to update the wiki page by yourself I'm open to suggestions Change By: Frédéric Camblor (19/Jul/13 7:42 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18499) SCM-Sync No Longer synchronising job configurations (only the jenkins config.xml)
Frédéric Camblor closed JENKINS-18499 as Duplicate SCM-Sync No Longer synchronising job configurations (only the jenkins config.xml) Duplicate of JENKINS-18526 Change By: Frédéric Camblor (19/Jul/13 9:11 AM) Status: Open Closed Resolution: Duplicate 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-16378) All build logs added and committed when renaming job
Frédéric Camblor commented on JENKINS-16378 All build logs added and committed when renaming job Have you tried with latest 0.0.7.1 ? Are you still facing the problem ? 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-15734) NullPointerException in ScmSyncConfigurationPlugin.getInstance
Frédéric Camblor updated JENKINS-15734 NullPointerException in ScmSyncConfigurationPlugin.getInstance Change By: Frédéric Camblor (19/Jul/13 10:31 PM) Priority: Blocker 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Frédéric Camblor commented on JENKINS-18715 scandir being triggered by FingerPrint.save Seems good news 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/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-16705) Native support for settings-security.xml (i. e. encrypted passwords)
Frédéric Camblor commented on JENKINS-16705 Native support for settings-security.xml (i. e. encrypted passwords) +1 on 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18597) provide the option to ignore system changes
Frédéric Camblor commented on JENKINS-18597 provide the option to ignore system changes I think ignoring whole system changes would be a bad thing, because it would imply undesirable behaviour to my POV (lots of commits are made by SYSTEM ... not keeping this changes would go against the backup feature of the plugin). But your use case is interesting though. Maybe could I track some "causes" for SYSTEM modification and allow to disable syncing on certain "causes" (one of the cause would be the hack by the EnvInject 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18500) SCM-Sync stops synchronising after deleting a job
Frédéric Camblor closed JENKINS-18500 as Duplicate SCM-Sync stops synchronising after deleting a job Change By: Frédéric Camblor (26/Jun/13 12:16 AM) Status: Open Closed Resolution: Duplicate 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-13593) Seems to not handle having builds in seperate folder
Frédéric Camblor commented on JENKINS-13593 Seems to not handle having builds in seperate folder Yup I don't see any other workaround ATM This issue is not on my top level priority list, so PR are welcome 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git As I said in the PR 14, this is not this simple The last time I looked at it, I was stuck on some svn/git differences in behaviour (having to rely on a generic layer for SCM manipulations is not always obvious). This makes me wondering if current issue is "fixable" given the current state of the project. It might be handled if I was dropping the use of scm API (that is to say, reimplement only my needed commands) and use jenkins' own credential api (see JENKINS-18129) 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git In the scm-sync-config plugin, there are 2 SCM API used (and bridged) nowadays : Jenkins SCM API : used mainly for authentication Maven SCM API : used mainly to provide an abstraction over "standard" scm commands Problem with SCM API are : I don't know them very well (don't think it is well documented either) I don't think it is as rich (in terms of abstractions) as the Maven SCM API (I don't think, for instance, that there is a generic method allowing to "commit" things on the repository ... since jenkins doesn't need to commit anything generally .. it only uses scm to checkout source files). On the SCM API side, problem is not with lack of generic layered methods, but differences in behaviour in these ones. For instance, update() with svn will do an `svn update` (thus, working copy will be up to date, and ready for subsequent modifications). A svn delete will then be taken into account directly. Whereas update() with a git impl will only do a `git fetch` (working copy not up-to-date (only origin references are updated)), thus we will need either a 'rebase' or 'merge' to include changes to push them on the upstream remote. These methods don't exist because they are too DVCS-oriented (and couldn't be implemented in non-DVCS scms). Moreover, changing things in SCM API takes time because adding a generic method needs every scm implementation to provide their impl for this new generic method This is the reason why I think the better solution will be to implement our own generic impl for plugin needs only 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/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Frédéric Camblor commented on JENKINS-17248 java.lang.NullPointerException by start I tried to migrate my local workspace from 1.424 to 1.508 and I encountered the problem, full stacktrace : Jun 16, 2013 1:35:42 PM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read /Users/fcamblor/Documents/projects/Jenkins-Plugins/global-build-stats/./work/global-build-stats.xml hudson.util.IOException2: Unable to read /Users/fcamblor/Documents/projects/Jenkins-Plugins/global-build-stats/./work/global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:170) at hudson.Plugin.load(Plugin.java:239) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.init(Jenkins.java:849) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$2.run(WebAppMain.java:214) Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null Debugging information cause-exception : java.lang.NullPointerException cause-message : null class : hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type : hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path: /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number : 2 version : null --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at hudson.XmlFile.unmarshal(XmlFile.java:166) ... 9 more Caused by: java.lang.NullPointerException at java.util.ArrayList.addAll(ArrayList.java:472) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:140) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) ... 18 more Jun 16, 2013 1:35:43 PM hudson.WebAppMain$2 run Problem is I cannot reproduce it now (problem fired only once, and after a jenkins restart it didn't pop anymore). If someone have any more input to reproduce the problem (backuped global-build-stats.xml for instance), it would be helpful for a fix. 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/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Frédéric Camblor commented on JENKINS-17248 java.lang.NullPointerException by start Doesn't reproduce the issue for me 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/groups/opt_out.
[JIRA] [redmine] (JENKINS-18211) password are commited in plain text
Frédéric Camblor commented on JENKINS-18211 password are commited in plain text Yep, this is related to redmine plugin It is not in the scope of the scm-sync-config plugin to alter the sync'ed files, particularly for the jenkins plugins galaxy 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/groups/opt_out.
[JIRA] [redmine] (JENKINS-18211) password are commited in plain text
Frédéric Camblor closed JENKINS-18211 as Not A Defect password are commited in plain text not related to scm-sync-config plugin. Please create a new issue for the redmine component (thus, component's lead will be automatically notified) Change By: Frédéric Camblor (06/Jun/13 8:14 AM) Status: Open Closed Resolution: NotADefect 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor commented on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing This would, for sure, be a gain in flexibility. I completely agree with you. ... but what I don't want is to give administrators the power to shoot themselves in the foot. To my POV, syncing an entire directory is not recommended. Since Jenkins is storing everyting in XML files, you'll often have lots of noise brought by lots of unneeded xml files in file hierarchies. It was the idea behind manual includes : target only important specific files that would be backed up. I know this is my personal POV which is not obviously shared by everyone I'll consider adding the exclude list someday, but it's not on the top of my todolist right now. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18207) scm-sync-configuration: Posibility to restore a configuration from a different repository location as the syncing location
Frédéric Camblor closed JENKINS-18207 as Duplicate scm-sync-configuration: Posibility to restore a configuration from a different repository location as the syncing location closing issue as duplicate of JENKINS-8527 Change By: Frédéric Camblor (05/Jun/13 12:36 PM) Status: Open Closed Resolution: Duplicate 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18211) password are commited in plain text
Frédéric Camblor commented on JENKINS-18211 password are commited in plain text I don't catch the point, where do you see unencrypted password ? What file ? What url ? 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor commented on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing Not really in favor to add excludes because, to my POV, it will complexify things I would rather be in favor to be more restrictive in the BasicPluginsConfigScmSyncStrategy default implementation (see here) WDYT ? 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor edited a comment on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing It would be the case if the BasicPluginsConfigScmSyncStrategy would only define a white list (more restricted as today) of sync'ed xml files. Then, users could play with manual includes feature to add their own files they want to sync. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18187) scm-sync-configuration: Posibility to exclude files/directories from syncing
Frédéric Camblor commented on JENKINS-18187 scm-sync-configuration: Posibility to exclude files/directories from syncing It would be the case if the BasicPluginsConfigScmSyncStrategy would only define a white list of sync'ed xml files. Then, users could play with manual includes feature to add their own files they want to sync. 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor created JENKINS-18124 Modularize scm-sync-config scm implementations Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 29/May/13 7:33 AM Description: Scm-sync-configuration is based on Maven SCM API Jenkins SCM API to provide a generic way to synchronize config files with multiple possible scm. Today, every possible SCM implementation (namely svn git) are bundled inside the scm-sync-configuration-plugin artefact, thus pulling every scm implementations even if you only rely on 1 of them. FYI, following dependencies will be pulled per scm implementation : maven-scm-provider's scm implementation (at the moment, either maven-scm-provider-svnjava or maven-scm-provider-gitexe) jenkins' plugin providing authentication support for your scm (at the moment, only org.jenkins-ci.plugins:subversion but we should consider org.jenkins-ci.plugins:git to have homogeneous git authentication support accross the plugin and jenkins stored credentials, see JENKINS-14506) This point is an important point because as soon as a plugin is depending on another plugin, jenkins will install both plugins when the root plugin is installed. This means when mercurial/perforce/whatever will be provided, when you will install the plugin on your jenkins instance, it will pull install lots of possible unwanted plugins on your instance. Another burden is the way scm implementation are maintained. I (Frédéric Camblor) will not be able to ensure every scm implementation will "work" : it is already a burden to ensure, for only 1 given scm implementation, that every possible scm protocols (namely svn / svn+ssh / http / https) are supported. This is something hard to test automatically because it needs to setup a subversion server handling every supported protocols. For more informations about this point, See JENKINS-8871. These are the reasons why I would like modularize the plugin. Technically, this should consist in : Modularize needed generic/helpful classes for scm manipulation in a scm-sync-configuration-api artefact Provide a maven parent pom for scm-sync-configuration's scm implementations, in order to help scm maintainer to only focus on their implementation, and not on the build / dependencies Externalize scm implementations into dedicated Jenkins plugins, relying on scm-sync-configuration-api and extending scm-sync-configuration-scm-parent pom Provide an @ExtensionPoint in the core, used by scm plugin implementors In terms of usability, this will imply for the user : To download not only the scm-sync-configuration-plugin but both scm-sync-configuration-plugin scm-sync-configuration-plugin-your scm impl(s) (for instance : scm-sync-configuration-plugin-subversion) The basic "none" scm implementation will be provided, and a message will be displayed to the user asking him to download at least one implementation if he didn't The plugin will not be backward compatible because we will go from (none/subversion/git) available implementations to (none) implementation only. I don't know, at the moment, In terms of maintenability, this will imply : Migration from an organization where I (Frederic Camblor) like a SPOF, to an organization where this is less the case : every scm implementor will be considered as its own maintainer (with dedicated component in jira project in github) The core will remain open to every contributor, particularly scm implementors (if one of them need an enhancement in the core, we'll have to talk about it but it will be welcomed) Project: Jenkins Priority: Major Reporter: Frédéric Camblor
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor updated JENKINS-18124 Modularize scm-sync-config scm implementations Change By: Frédéric Camblor (29/May/13 7:40 AM) Description: Scm-sync-configurationisbasedonMavenSCMAPIJenkinsSCMAPItoprovideagenericwaytosynchronizeconfigfileswithmultiplepossiblescm.Today,everypossibleSCMimplementation(namelysvngit)arebundledinsidethescm-sync-configuration-pluginartefact,thuspullingeveryscmimplementationsevenifyouonlyrelyon1ofthem.FYI,followingdependencieswillbepulled_perscmimplementation_:- * maven-scm-provider * sscmimplementation(atthemoment,eithermaven-scm-provider-svnjavaormaven-scm-provider-gitexe)- jenkins Jenkins pluginproviding * authenticationsupport * foryourscm(atthemoment,onlyorg.jenkins-ci.plugins:subversionbutweshouldconsiderorg.jenkins-ci.plugins:gittohavehomogeneousgitauthenticationsupportaccrossthepluginandjenkinsstoredcredentials,seeJENKINS-14506)Thispointisanimportantpointbecauseassoonasapluginisdependingonanotherplugin,jenkinswillinstallbothpluginswhentherootpluginisinstalled.Thismeans when once [mercurial|https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/9]/perforce/whateverwillbe provided supported ,whenyouwillinstallthepluginonyourjenkinsinstance,itwillpullinstalllotsofpossibleunwantedpluginsonyourinstance.Anotherburdenisthewayscm implementation implementations aremaintained.I(FrédéricCamblor)willnotbeabletoensure*every*scmimplementationwill just work:itisalreadyaburden forme toensure,foronly1givenscmimplementation,thateverypossiblescmprotocols(namelysvn/svn+ssh/http/https)aresupported (SeeJENKINS-8871) .Thisissomethinghardtotest automatically (andIdontevenspeakabout*automatic*testing) becauseitneedstosetupasubversionserverhandlingeverysupportedprotocols. Formoreinformationsaboutthispoint,SeeJENKINS-8871. ThesearethereasonswhyIwouldlike to modularizetheplugin.Technically,thisshouldconsistin:-Modularizeneededgeneric/helpfulclassesforscmmanipulationinascm-sync-configuration-apiartefact-Provideamavenparentpomforscm-sync-configurationsscm implementations implementors ,inordertohelpscmmaintainertoonlyfocusontheirimplementation,andnotonthebuild/dependencies fortheplugin -ExternalizescmimplementationsintodedicatedJenkinsplugins,relyingonscm-sync-configuration-apiandextendingscm-sync-configuration-scm-parentpom-Providean[@ExtensionPoint|https://wiki.jenkins-ci.org/display/JENKINS/Extension+points]inthecore,usedbyscmpluginimplementors toplugtheirimplementation Intermsofusability,thiswillimplyfortheuser:-Todownloadnotonlythescm-sync-configuration-pluginbutbothscm-sync-configuration-pluginscm-sync-configuration-plugin-yourscmimpl(s)(forinstance:scm-sync-configuration-plugin-subversion)-Thebasicnonescmimplementationwillbeprovided,andamessagewillbedisplayedtotheuseraskinghimtodownloadatleastoneimplementationifhedidnt- * Thepluginwillnotbebackwardcompatible * becausewewillgofrom(none/subversion/git)availableimplementationsto(none)implementationonly.Idontknow,atthemoment, howIcouldhandlethisbackwardincompatibility(ifyouhaveideas,donthesitatetosubmitthemincomments). MaybecouldIrenamethepluginanddeprecatetheexistingone?Idunno. Intermsofmaintenability,thiswillimply:-MigrationfromanorganizationwhereI(FredericCamblor) like am a * SPOF * ,toanorganizationwherethisis*less*thecase:everyscmimplementorwillbeconsideredas itsown aplugin maintainer ( withdedicatedcomponentinjira , projectingithub ) ,*andresponsibilities*. -Thecorewillremainopentoeverycontributor,particularlyscmimplementors(ifoneofthemneedanenhancementinthecore,wellhavetotalkaboutitbutitwillbewelcomed) 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor updated JENKINS-18124 Modularize scm-sync-config scm implementations Change By: Frédéric Camblor (29/May/13 7:52 AM) Description: Scm-sync-configurationisbasedonMavenSCMAPIJenkinsSCMAPItoprovideagenericwaytosynchronizeconfigfileswithmultiplepossiblescm.Today,everypossibleSCMimplementation(namelysvngit)arebundledinsidethescm-sync-configuration-pluginartefact,thuspullingeveryscmimplementationsevenifyouonlyrelyon1ofthem.FYI,followingdependencieswillbepulled_perscmimplementation_:-*maven-scm-provider*sscmimplementation(atthemoment, either both maven-scm-provider-svnjava or and maven-scm-provider-gitexe)-Jenkinspluginproviding*authenticationsupport*foryourscm(atthemoment,onlyorg.jenkins-ci.plugins:subversionbutweshouldconsiderorg.jenkins-ci.plugins:gittohavehomogeneousgitauthenticationsupportaccrossthepluginandjenkinsstoredcredentials,seeJENKINS-14506)Thispointisanimportantpointbecauseassoonasapluginisdependingonanotherplugin,jenkinswillinstallbothpluginswhentherootpluginisinstalled.Thismeansonce[mercurial|https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/9]/perforce/whateverwillbesupported,whenyouwillinstallthepluginonyourjenkinsinstance,itwillpullinstalllotsofpossibleunwantedpluginsonyourinstance.Anotherburdenisthewayscmimplementationsaremaintained.I(FrédéricCamblor)willnotbeabletoensure*every*scmimplementationwilljustwork:itisalreadyaburdenformetoensure,foronly1givenscmimplementation,thateverypossiblescmprotocols(namelysvn/svn+ssh/http/https)aresupported(SeeJENKINS-8871).Thisissomethinghardtotest(andIdontevenspeakabout*automatic*testing)becauseitneedstosetupasubversionserverhandlingeverysupportedprotocols.ThesearethereasonswhyIwouldliketomodularizetheplugin.Technically,thisshouldconsistin:-Modularizeneededgeneric/helpfulclassesforscmmanipulationinascm-sync-configuration-apiartefact-Provideamavenparentpomforscm-sync-configurationsscmimplementors,inordertohelpscmmaintainertoonlyfocusontheirimplementation,andnotonthebuild/dependenciesfortheplugin-ExternalizescmimplementationsintodedicatedJenkinsplugins,relyingonscm-sync-configuration-apiandextendingscm-sync-configuration-scm-parentpom-Providean[@ExtensionPoint|https://wiki.jenkins-ci.org/display/JENKINS/Extension+points]inthecore,usedbyscmpluginimplementorstoplugtheirimplementationIntermsofusability,thiswillimplyfortheuser:-Todownloadnotonlythescm-sync-configuration-pluginbutbothscm-sync-configuration-pluginscm-sync-configuration-plugin-yourscmimpl(s)(forinstance:scm-sync-configuration-plugin-subversion)-Thebasicnonescmimplementationwillbeprovided,andamessagewillbedisplayedtotheuseraskinghimtodownloadatleastoneimplementationifhedidnt-*Thepluginwillnotbebackwardcompatible*becausewewillgofrom(none/subversion/git)availableimplementationsto(none)implementationonly.Idontknow,atthemoment,howIcouldhandlethisbackwardincompatibility(ifyouhaveideas,donthesitatetosubmitthemincomments).MaybecouldIrenamethepluginanddeprecatetheexistingone?Idunno.Intermsofmaintenability,thiswillimply:-MigrationfromanorganizationwhereI(FredericCamblor)ama*SPOF*,toanorganizationwherethisis*less*thecase:everyscmimplementorwillbeconsideredasapluginmaintainerwithdedicatedcomponentinjira,projectingithub,*andresponsibilities*.-Thecorewillremainopentoeverycontributor,particularlyscmimplementors(ifoneofthemneedanenhancementinthecore,wellhavetotalkaboutitbutitwillbewelcomed) 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor updated JENKINS-18124 Modularize scm-sync-config scm implementations Change By: Frédéric Camblor (29/May/13 7:56 AM) Description: Scm-sync-configurationisbasedonMavenSCMAPIJenkinsSCMAPItoprovideagenericwaytosynchronizeconfigfileswithmultiplepossiblescm.Today,everypossibleSCMimplementation(namelysvngit)arebundledinsidethescm-sync-configuration-pluginartefact,thuspullingeveryscmimplementationsevenifyouonlyrelyon1ofthem.FYI,followingdependencieswillbepulled_perscmimplementation_:-*maven-scm-provider*sscmimplementation(atthemoment,bothmaven-scm-provider-svnjavaandmaven-scm-provider-gitexe)-Jenkinspluginproviding*authenticationsupport*foryourscm(atthemoment,onlyorg.jenkins-ci.plugins:subversionbutweshouldconsiderorg.jenkins-ci.plugins:gittohavehomogeneousgitauthenticationsupportaccrossthepluginandjenkinsstoredcredentials,seeJENKINS-14506)Thispointisanimportantpointbecauseassoonasapluginisdependingonanotherplugin,jenkinswillinstallbothpluginswhentherootpluginisinstalled.Thismeansonce[mercurial|https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/9]/perforce/whateverwillbesupported,whenyouwillinstallthepluginonyourjenkinsinstance,itwillpullinstalllotsofpossibleunwantedpluginsonyourinstance.Anotherburdenisthewayscmimplementationsaremaintained.I(FrédéricCamblor)willnotbeabletoensure*every*scmimplementationwilljustwork:itisalreadyaburdenformetoensure,foronly1givenscmimplementation,thateverypossiblescmprotocols(namelysvn/svn+ssh/http/https)aresupported(SeeJENKINS-8871).Thisissomethinghardtotest(andIdontevenspeakabout*automatic*testing)becauseitneedstosetupasubversionserverhandlingeverysupportedprotocols.ThesearethereasonswhyIwouldliketomodularizetheplugin.Technically,thisshouldconsistin:-Modularizeneededgeneric/helpfulclassesforscmmanipulationinascm-sync-configuration-apiartefact-Provideamavenparentpomforscm-sync-configurationsscmimplementors,inordertohelpscmmaintainertoonlyfocusontheirimplementation,andnotonthebuild/dependenciesfortheplugin-ExternalizescmimplementationsintodedicatedJenkinsplugins,relyingonscm-sync-configuration-apiandextendingscm-sync-configuration-scm-parentpom-Providean[@ExtensionPoint|https://wiki.jenkins-ci.org/display/JENKINS/Extension+points]inthecore,usedbyscmpluginimplementorstoplugtheirimplementationIntermsofusability,thiswillimplyfortheuser:-Todownloadnotonlythescm-sync-configuration-pluginbutbothscm-sync-configuration-pluginscm-sync-configuration-plugin-yourscmimpl(s)(forinstance:scm-sync-configuration-plugin-subversion)-Thebasicnonescmimplementationwillbeprovided,andamessagewillbedisplayedtotheuseraskinghimtodownloadatleastoneimplementationifhedidnt-*Thepluginwillnotbebackwardcompatible*becausewewillgofrom(none/subversion/git)availableimplementationsto(none)implementationonly.Idontknow,atthemoment,howIcouldhandlethisbackwardincompatibility(ifyouhaveideas,donthesitatetosubmitthemincomments).MaybecouldIrenamethepluginanddeprecatetheexistingone?Idunno. -Lifecyclebetweencoreandscmimplementationswontbethesame:abugfix/improvementinanscmimplementationwontneedareleaseofthecore Drawbackforthisiswewillhavetotrackapiincompatibilitiesinthecore,andalignscmimplementationswhenneeded. Intermsofmaintenability,thiswillimply:-MigrationfromanorganizationwhereI(FredericCamblor)ama*SPOF*,toanorganizationwherethisis*less*thecase:everyscmimplementorwillbeconsideredasapluginmaintainerwithdedicatedcomponentinjira,projectingithub,*andresponsibilities*.-Thecorewillremainopentoeverycontributor,particularlyscmimplementors(ifoneofthemneedanenhancementinthecore,wellhavetotalkaboutitbutitwillbewelcomed) 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
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor updated JENKINS-18124 Modularize scm-sync-config scm implementations Change By: Frédéric Camblor (29/May/13 7:59 AM) Description: Scm-sync-configurationisbasedonMavenSCMAPIJenkinsSCMAPItoprovideagenericwaytosynchronizeconfigfileswithmultiplepossiblescm.Today,everypossibleSCMimplementation(namelysvngit)arebundledinsidethescm-sync-configuration-pluginartefact,thuspullingeveryscmimplementationsevenifyouonlyrelyon1ofthem.FYI,followingdependencieswillbepulled_perscmimplementation_:-*maven-scm-provider*sscmimplementation(atthemoment,bothmaven-scm-provider-svnjavaandmaven-scm-provider-gitexe)-Jenkinspluginproviding*authenticationsupport*foryourscm(atthemoment,onlyorg.jenkins-ci.plugins:subversionbutweshouldconsiderorg.jenkins-ci.plugins:gittohavehomogeneousgitauthenticationsupportaccrossthepluginandjenkinsstoredcredentials,seeJENKINS-14506)Thispointisanimportantpointbecauseassoonasapluginisdependingonanotherplugin,jenkinswillinstallbothpluginswhentherootpluginisinstalled.Thismeansonce[mercurial|https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/9]/perforce/whateverwillbesupported,whenyouwillinstallthepluginonyourjenkinsinstance,itwillpullinstalllotsofpossibleunwantedpluginsonyourinstance.Anotherburdenisthewayscmimplementationsaremaintained.I(FrédéricCamblor)willnotbeabletoensure*every*scmimplementationwilljustwork:itisalreadyaburdenformetoensure,foronly1givenscmimplementation,thateverypossiblescmprotocols(namelysvn/svn+ssh/http/https)aresupported(SeeJENKINS-8871).Thisissomethinghardtotest(andIdontevenspeakabout*automatic*testing)becauseitneedstosetupasubversionserverhandlingeverysupportedprotocols.ThesearethereasonswhyIwouldliketomodularizetheplugin.Technically,thisshouldconsistin:-Modularizeneededgeneric/helpfulclassesforscmmanipulationinascm-sync-configuration-apiartefact-Provideamavenparentpomforscm-sync-configurationsscmimplementors,inordertohelpscmmaintainertoonlyfocusontheirimplementation,andnotonthebuild/dependenciesfortheplugin-ExternalizescmimplementationsintodedicatedJenkinsplugins,relyingonscm-sync-configuration-apiandextendingscm-sync-configuration-scm-parentpom-Providean[@ExtensionPoint|https://wiki.jenkins-ci.org/display/JENKINS/Extension+points]inthecore,usedbyscmpluginimplementorstoplugtheirimplementationIntermsofusability,thiswillimplyfortheuser:-Todownloadnotonlythescm-sync-configuration-pluginbutbothscm-sync-configuration-pluginscm-sync-configuration-plugin-yourscmimpl(s)(forinstance:scm-sync-configuration-plugin-subversion)-Thebasicnonescmimplementationwillbeprovided,andamessagewillbedisplayedtotheuseraskinghimtodownloadatleastoneimplementationifhedidnt-*Thepluginwillnotbebackwardcompatible*becausewewillgofrom(none/subversion/git)availableimplementationsto(none)implementationonly.Idontknow,atthemoment,howIcouldhandlethisbackwardincompatibility(ifyouhaveideas,donthesitatetosubmitthemincomments).MaybecouldIrenamethepluginanddeprecatetheexistingone?Idunno.-Lifecyclebetweencoreandscmimplementationswontbethesame:abugfix/improvementinanscmimplementationwontneedareleaseofthecoreDrawbackforthisiswewillhavetotrackapiincompatibilitiesinthecore,andalignscmimplementationswhenneeded. Goalistoavoiderrorswhencoreisupgradedandimplementationsarenot(eventually,wecouldenforcethisproblematicinscm-sync-config-api) Intermsofmaintenability,thiswillimply:-MigrationfromanorganizationwhereI(FredericCamblor)ama*SPOF*,toanorganizationwherethisis*less*thecase:everyscmimplementorwillbeconsideredasapluginmaintainerwithdedicatedcomponentinjira,projectingithub,*andresponsibilities*.-Thecorewillremainopentoeverycontributor,particularlyscmimplementors(ifoneofthemneedanenhancementinthecore,wellhavetotalkaboutitbutitwillbewelcomed) 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
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor updated JENKINS-18124 Modularize scm-sync-config scm implementations Change By: Frédéric Camblor (29/May/13 8:00 AM) Description: Scm-sync-configurationisbasedonMavenSCMAPIJenkinsSCMAPItoprovideagenericwaytosynchronizeconfigfileswithmultiplepossiblescm.Today,everypossibleSCMimplementation(namelysvngit)arebundledinsidethescm-sync-configuration-pluginartefact,thuspullingeveryscmimplementationsevenifyouonlyrelyon1ofthem.FYI,followingdependencieswillbepulled_perscmimplementation_:-*maven-scm-provider*sscmimplementation(atthemoment,bothmaven-scm-provider-svnjavaandmaven-scm-provider-gitexe)-Jenkinspluginproviding*authenticationsupport*foryourscm(atthemoment,onlyorg.jenkins-ci.plugins:subversionbutweshouldconsiderorg.jenkins-ci.plugins:gittohavehomogeneousgitauthenticationsupportaccrossthepluginandjenkinsstoredcredentials,seeJENKINS-14506)Thispointisanimportantpointbecauseassoonasapluginisdependingonanotherplugin,jenkinswillinstallbothpluginswhentherootpluginisinstalled.Thismeansonce[mercurial|https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/9]/perforce/whateverwillbesupported,whenyouwillinstallthepluginonyourjenkinsinstance,itwillpullinstalllotsofpossibleunwantedpluginsonyourinstance.Anotherburdenisthewayscmimplementationsaremaintained.I(FrédéricCamblor)willnotbeabletoensure*every*scmimplementationwilljustwork:itisalreadyaburdenformetoensure,foronly1givenscmimplementation,thateverypossiblescmprotocols(namelysvn/svn+ssh/http/https)aresupported(SeeJENKINS-8871).Thisissomethinghardtotest(andIdontevenspeakabout*automatic*testing)becauseitneedstosetupasubversionserverhandlingeverysupportedprotocols.ThesearethereasonswhyIwouldliketomodularizetheplugin.Technically,thisshouldconsistin:-Modularizeneededgeneric/helpfulclassesforscmmanipulationinascm-sync-configuration-apiartefact-Provideamavenparentpomforscm-sync-configurationsscmimplementors,inordertohelpscmmaintainertoonlyfocusontheirimplementation,andnotonthebuild/dependenciesfortheplugin-ExternalizescmimplementationsintodedicatedJenkinsplugins,relyingonscm-sync-configuration-apiandextendingscm-sync-configuration-scm-parentpom-Providean[@ExtensionPoint|https://wiki.jenkins-ci.org/display/JENKINS/Extension+points]inthecore,usedbyscmpluginimplementorstoplugtheirimplementationIntermsofusability,thiswillimplyfortheuser:-Todownloadnotonlythescm-sync-configuration-pluginbutbothscm-sync-configuration-pluginscm-sync-configuration-plugin-yourscmimpl(s)(forinstance:scm-sync-configuration-plugin-subversion)-Thebasicnonescmimplementationwillbeprovided,andamessagewillbedisplayedtotheuseraskinghimtodownloadatleastoneimplementationifhedidnt-*Thepluginwillnotbebackwardcompatible*becausewewillgofrom(none/subversion/git)availableimplementationsto(none)implementationonly.Idontknow,atthemoment,howIcouldhandlethisbackwardincompatibility(ifyouhaveideas,donthesitatetosubmitthemincomments).MaybecouldIrenamethepluginanddeprecatetheexistingone?Idunno.-Lifecyclebetweencoreandscmimplementationswontbethesame:abugfix/improvementinanscmimplementationwontneedareleaseofthecoreDrawbackforthisiswewillhavetotrackapiincompatibilitiesinthecore,andalignscmimplementationswhenneeded.Goalistoavoiderrorswhencoreisupgradedandimplementationsarenot(eventually,wecouldenforcethisdetectioninscm-sync-config-api)Intermsofmaintenability,thiswillimply:-MigrationfromanorganizationwhereI(FredericCamblor)ama*SPOF*,toanorganizationwherethisis*less*thecase:everyscmimplementorwillbeconsideredasapluginmaintainerwithdedicatedcomponentinjira,projectingithub,*andresponsibilities*.-Thecorewillremainopentoeverycontributor,particularlyscmimplementors(ifoneofthemneedanenhancementinthecore,wellhavetotalkaboutitbutitwillbewelcomed) DonthesitatetoprovideyourPOVinthecomments,Imopenedtothem 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
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor updated JENKINS-18124 Modularize scm-sync-config scm implementations Change By: Frédéric Camblor (29/May/13 7:59 AM) Description: Scm-sync-configurationisbasedonMavenSCMAPIJenkinsSCMAPItoprovideagenericwaytosynchronizeconfigfileswithmultiplepossiblescm.Today,everypossibleSCMimplementation(namelysvngit)arebundledinsidethescm-sync-configuration-pluginartefact,thuspullingeveryscmimplementationsevenifyouonlyrelyon1ofthem.FYI,followingdependencieswillbepulled_perscmimplementation_:-*maven-scm-provider*sscmimplementation(atthemoment,bothmaven-scm-provider-svnjavaandmaven-scm-provider-gitexe)-Jenkinspluginproviding*authenticationsupport*foryourscm(atthemoment,onlyorg.jenkins-ci.plugins:subversionbutweshouldconsiderorg.jenkins-ci.plugins:gittohavehomogeneousgitauthenticationsupportaccrossthepluginandjenkinsstoredcredentials,seeJENKINS-14506)Thispointisanimportantpointbecauseassoonasapluginisdependingonanotherplugin,jenkinswillinstallbothpluginswhentherootpluginisinstalled.Thismeansonce[mercurial|https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/9]/perforce/whateverwillbesupported,whenyouwillinstallthepluginonyourjenkinsinstance,itwillpullinstalllotsofpossibleunwantedpluginsonyourinstance.Anotherburdenisthewayscmimplementationsaremaintained.I(FrédéricCamblor)willnotbeabletoensure*every*scmimplementationwilljustwork:itisalreadyaburdenformetoensure,foronly1givenscmimplementation,thateverypossiblescmprotocols(namelysvn/svn+ssh/http/https)aresupported(SeeJENKINS-8871).Thisissomethinghardtotest(andIdontevenspeakabout*automatic*testing)becauseitneedstosetupasubversionserverhandlingeverysupportedprotocols.ThesearethereasonswhyIwouldliketomodularizetheplugin.Technically,thisshouldconsistin:-Modularizeneededgeneric/helpfulclassesforscmmanipulationinascm-sync-configuration-apiartefact-Provideamavenparentpomforscm-sync-configurationsscmimplementors,inordertohelpscmmaintainertoonlyfocusontheirimplementation,andnotonthebuild/dependenciesfortheplugin-ExternalizescmimplementationsintodedicatedJenkinsplugins,relyingonscm-sync-configuration-apiandextendingscm-sync-configuration-scm-parentpom-Providean[@ExtensionPoint|https://wiki.jenkins-ci.org/display/JENKINS/Extension+points]inthecore,usedbyscmpluginimplementorstoplugtheirimplementationIntermsofusability,thiswillimplyfortheuser:-Todownloadnotonlythescm-sync-configuration-pluginbutbothscm-sync-configuration-pluginscm-sync-configuration-plugin-yourscmimpl(s)(forinstance:scm-sync-configuration-plugin-subversion)-Thebasicnonescmimplementationwillbeprovided,andamessagewillbedisplayedtotheuseraskinghimtodownloadatleastoneimplementationifhedidnt-*Thepluginwillnotbebackwardcompatible*becausewewillgofrom(none/subversion/git)availableimplementationsto(none)implementationonly.Idontknow,atthemoment,howIcouldhandlethisbackwardincompatibility(ifyouhaveideas,donthesitatetosubmitthemincomments).MaybecouldIrenamethepluginanddeprecatetheexistingone?Idunno.-Lifecyclebetweencoreandscmimplementationswontbethesame:abugfix/improvementinanscmimplementationwontneedareleaseofthecoreDrawbackforthisiswewillhavetotrackapiincompatibilitiesinthecore,andalignscmimplementationswhenneeded.Goalistoavoiderrorswhencoreisupgradedandimplementationsarenot(eventually,wecouldenforcethis problematic detection inscm-sync-config-api)Intermsofmaintenability,thiswillimply:-MigrationfromanorganizationwhereI(FredericCamblor)ama*SPOF*,toanorganizationwherethisis*less*thecase:everyscmimplementorwillbeconsideredasapluginmaintainerwithdedicatedcomponentinjira,projectingithub,*andresponsibilities*.-Thecorewillremainopentoeverycontributor,particularlyscmimplementors(ifoneofthemneedanenhancementinthecore,wellhavetotalkaboutitbutitwillbewelcomed) 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
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor commented on JENKINS-18124 Modularize scm-sync-config scm implementations @Nicolas I agree with you on the fact that only a little set of maven-scm is used. And relying on it shows its limits as soon as a feature is not "generically" available for every scms (see JENKINS-14841). So your proposal makes sense. What I'm not confident about this proposal is the way authentication will be handled on SCM. Is Jenkins SCM API providing generic way to authenticate against stored credentials in jenkins ? If it would be the case, it would be great ! @Henri Dependency against core is the burden of every plugin maintainers. But I don't know there is a better way to handle this. This was the intention of the plugin-compat-tester .. but I didn't have enough time recently to improve it 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18124) Modularize scm-sync-config scm implementations
Frédéric Camblor commented on JENKINS-18124 Modularize scm-sync-config scm implementations @Nicolas The main goal of maven parent is to provide some tricky things like the plexus components merging. ... Only needed if we stay with maven-scm-api. If there isn't any tricky build part, no parent will be needed. 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/groups/opt_out.
