[JIRA] [scm-sync-configuration] (JENKINS-17946) Include a list of plugins installed
Samu Wikstedt commented on JENKINS-17946 Include a list of plugins installed You are right about the plugin versions issue; Following LTS jenkins update cycle, is nicely working solution for us. But true, that might not be the case in all users. 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-17946) Include a list of plugins installed
Samu Wikstedt resolved JENKINS-17946 as Not A Defect Include a list of plugins installed BAcking up running jenkins is highly dependent on the matter how jenkins maintainer want's to back it up. --- It's better to leave needed plugin list generation to one own solution(s) that meets ones requirements. Change By: Samu Wikstedt (21/May/13 6:49 AM) Status: Open Resolved 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-17946) Include a list of plugins installed
Samu Wikstedt
commented on JENKINS-17946
Include a list of plugins installed
I guess responsibility of scm-sync-configuration depends on the point of view: Meaning, if purpose is to have backup stored in a safe place, which can be restored after total disaster (for example disk failure, stolen hardware, fire ...) then list of installed plugins is needed. My experienses are that if you try to restore a xml files that have configuration of plugins not currently installed, Jenkins gets quite confused.
If the purpose is just to have SCM repository where old changes in working jenkins configuration can be fetched if needed, this plugin works just fine. And I am not intended to start a debate of the purpose of the plugin. After all it is great tool for my purposes already. So, I am just suggesting widening the scope of the plugin since I think that it could be done quite easily - However, since my java programming skills are severely limited , I might be mistaken on that one
Since I do lack java programming skills, developing plugin is out of my scope. However I do have done a Jenkins restore successfully with method that is more simple that your way of getting plugin list... Now I'm just wondering whether I had more simple plugins than you have had... So what information is lost with method described below:
Prerequisite are:
Jenkins installation, which have configuration backed up with scm-sync-configuration.
List of installed plugins is created with help of jenkins-cli and stripped to more simple list and included to backup:
java -jar jenkins-cli.jar -s http://yourjenkinsurl:8080/ list-plugins plugins.txt
awk '{print $1}' plugins.txt plugins_tripped.txt
Output is a simple list which have simple list of plugin names.
The actual restoring config has these steps:
have new HW-platform with working OS for your jenkins
install fresh jenkins on top of that
Install all plugins from jenkins update site, use the plugins-list from backup:
cat plugins_tripped.txt | xargs java -jar jenkins-cli.jar -s http://yourjenkinsurl:8080/ install-plugin
Shut down jenkins, do svn checkout (or GIT pull) to a temporary folder and copy everything to jenkins home folder, start jenkins and you should have working jenkins again up and running.
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-17946) Include a list of plugins installed
Frédéric Camblor commented on JENKINS-17946 Include a list of plugins installed Using the jenkins-cli you need : To have an open Jenkins (no authent) : Using jenkins-cli doesn't seem to handle credentials, or have to set up a ssh private key which seems unsafe to me In your example, you don't retrieve plugins' versions, and it seems the install-plugin will install the latest version of every plugins, which is undesirable to my POV 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-17946) Include a list of plugins installed
Samu Wikstedt created JENKINS-17946 Include a list of plugins installed Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 14/May/13 11:48 AM Description: SCMsync is great plugin for having backup in safe place, but if you ever need to restore configuration after total disaster, it lacks information of plugins that were installed. It would be good to have this plugin to create a list of plugins installed to jenkins and store it to svn/git with other config data. Project: Jenkins Priority: Major Reporter: Samu Wikstedt 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-17946) Include a list of plugins installed
Frédéric Camblor commented on JENKINS-17946 Include a list of plugins installed I don't think it is the responsibility of the plugin to "create" the data listing every plugins. If you can find (or implement, it shouldn't be very difficult) a plugin which : Browse every directories in JENKINS_HOME/plugins/ folder (every folder = 1 installed plugin) For every folder, look into JENKINS_HOME/plugins/plugin/META-INF/maven/org.jenkins-ci.plugins/ant/pom.properties for the GAV of the plugin List every of these GAV and persist it in a file (no matter the type) on JENKINS_HOME Then this file could be sync'ed with scm-sync-config plugin (easily with a custom include). WDYT ? It is an easy plugin to implement, and doesn't need to have any knowledge on the scm-sync-config 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-17946) Include a list of plugins installed
Frédéric Camblor edited a comment on JENKINS-17946 Include a list of plugins installed I don't think it is the responsibility of the plugin to "create" the data listing every plugins. If you can find (or implement, it shouldn't be very difficult) a plugin which : Browse every directories in JENKINS_HOME/plugins/ folder (every folder = 1 installed plugin) For every folder, look into JENKINS_HOME/plugins/plugin/META-INF/maven/org.jenkins-ci.plugins/ant/pom.properties for the GAV of the plugin List every of these GAV and persist it in a file (no matter the type) on JENKINS_HOME Then this file could be sync'ed with scm-sync-config plugin (easily with a custom include). WDYT ? It is an easy plugin to implement, and doesn't need to have any knowledge on the scm-sync-config plugin The most complicated thing here is the "when" will this plugin be run : ideally, would be nice to run it on jenkins start and/or plugin update is performed 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.
