[JIRA] (JENKINS-41754) thinBackup run custom script after backup
Title: Message Title Thomas Fürer commented on JENKINS-41754 Re: thinBackup run custom script after backup thank you for your ideas. I started a new version branch (2.0) some time ago, which will cover exactly your requests in a way that the different action can be implemented in where or how the backup is stored. Unfortently I'm limited in time so the progress is very bad... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29292) Add support for scriptler.
Title: Message Title Thomas Fürer resolved as Fixed a solution to back up additional files should be part of 1.8.0. please upgrade and try again, but do not hesidate if it do not work as expected Jenkins / JENKINS-29292 Add support for scriptler. Change By: Thomas Fürer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-30144) thinBackup does not backup Slave settings
Title: Message Title Thomas Fürer resolved as Fixed a solution to back up additional files should be part of 1.8.0. please upgrade and try again, but do not hesidate if it do not work as expected Jenkins / JENKINS-30144 thinBackup does not backup Slave settings Change By: Thomas Fürer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-31151) scm-sync-configuration does not track promotions/config.xml
Title: Message Title Thomas Fürer resolved as Won't Fix with 1.8.0 it should be possible to specify additional backup relevant files so please try again, but don't hesidate to reopen the issue if it do not work for you Jenkins / JENKINS-31151 scm-sync-configuration does not track promotions/config.xml Change By: Thomas Fürer Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-35324) Support restoring secrets
Title: Message Title Thomas Fürer resolved as Done should be part of 1.8.0 Jenkins / JENKINS-35324 Support restoring secrets Change By: Thomas Fürer Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36562) Wrong link to JIRA issues from plugin page
Title: Message Title Thomas Fürer resolved as Fixed JENKINS-16997 is already fixed Jenkins / JENKINS-36562 Wrong link to JIRA issues from plugin page Change By: Thomas Fürer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36758) Thinbackup release 1.7.6 not available in jenkins update center
Title: Message Title Thomas Fürer resolved as Won't Fix ThinBackup with Version 1.8.0 is out now. Jenkins / JENKINS-36758 Thinbackup release 1.7.6 not available in jenkins update center Change By: Thomas Fürer Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-39546) thinBackup fails to backup "domain\user" folders under $JENKINS_HOME/users
Title: Message Title Thomas Fürer closed an issue as Not A Defect Jenkins / JENKINS-39546 thinBackup fails to backup "domain\user" folders under $JENKINS_HOME/users Change By: Thomas Fürer Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39546) thinBackup fails to backup "domain\user" folders under $JENKINS_HOME/users
Title: Message Title Thomas Fürer commented on JENKINS-39546 Re: thinBackup fails to backup "domain\user" folders under $JENKINS_HOME/users added an issue at apache.org common-io project IO-517 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39546) thinBackup fails to backup "domain\user" folders under $JENKINS_HOME/users
Title: Message Title Thomas Fürer commented on JENKINS-39546 Re: thinBackup fails to backup "domain\user" folders under $JENKINS_HOME/users looks like that the path is incorrect reagrding the separators. the separator between domain and name is probably interpreted like a path separator. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [thinBackup] (JENKINS-23377) cron driven backups never happen
Thomas Fürer updated JENKINS-23377 cron driven backups never happen reduced to minor because workaround is available and working an different systems Change By: Thomas Fürer (17/Dec/14 4:16 PM) Priority: Blocker Minor 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] [thinBackup] (JENKINS-24793) Issue while restoring backup from thinbackup plugin
Thomas Fürer assigned JENKINS-24793 to appannie appannie Issue while restoring backup from thinbackup plugin Change By: Thomas Fürer (22/Sep/14 4:52 PM) Assignee: ThomasFürer appannieappannie 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] [thinBackup] (JENKINS-24793) Issue while restoring backup from thinbackup plugin
Thomas Fürer resolved JENKINS-24793 as Not A Defect Issue while restoring backup from thinbackup plugin Backup and restore to different version are not guaranteed to work. because the backup/restore only (re)store the file it could cause problems when the file content is upgraded. Try to install the same version on the target first and afterwards try to upgrade. In the case this also not work you should reopen this issue. Change By: Thomas Fürer (22/Sep/14 4:52 PM) 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/d/optout.
[JIRA] [core] (JENKINS-24364) Cannot Delete Job Item for Shared SCM settings
Thomas Fürer created JENKINS-24364 Cannot Delete Job Item for Shared SCM settings Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 21/Aug/14 9:59 AM Description: GIVEN: a job located in a folder structure using a SCM configuration of a different job in the same folder structure (specified with somefolder/somefolder/job) WHEN: try to delete the job THEN: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [core] (JENKINS-24364) Cannot Delete Job Item for Shared SCM settings
Thomas Fürer commented on JENKINS-24364 Cannot Delete Job Item for Shared SCM settings WORKAROUND: setting the SCM configuration to NONE will allow to delete the job This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder] (JENKINS-24364) Cannot Delete Job Item for Shared SCM settings
Thomas Fürer updated JENKINS-24364 Cannot Delete Job Item for Shared SCM settings Change By: Thomas Fürer (21/Aug/14 10:02 AM) Component/s: cloudbees-folder Component/s: scm-api 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] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option Backup build results is switched on
Thomas Fürer commented on JENKINS-24302 backup ends before all jobs are backed-up if option Backup build results is switched on OK, which version of thinbackup do you have installed on wich windows 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] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option Backup build results is switched on
Thomas Fürer commented on JENKINS-24302 backup ends before all jobs are backed-up if option Backup build results is switched on Hi markus, Could it be that you have symbolic links in your buildresult folder? currently not all OS (e.g. windows) do not support symbolic links... 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] [thinBackup] (JENKINS-23377) cron driven backups never happen
Thomas Fürer updated JENKINS-23377 cron driven backups never happen raise the priority, because it blocks a uiser with a regular backup on a very new jenkins release. Change By: Thomas Fürer (10/Jun/14 6:03 AM) Priority: Major Blocker 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] [thinBackup] (JENKINS-22630) Log when backup is finished/complete
Thomas Fürer closed JENKINS-22630 as Duplicate Log when backup is finished/complete JENKINS-18757 Change By: Thomas Fürer (10/Jun/14 6: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] [thinBackup] (JENKINS-20547) Support of symbolic links which are not done by jenkins
Thomas Fürer updated JENKINS-20547 Support of symbolic links which are not done by jenkins Change By: Thomas Fürer (10/Jun/14 6:09 AM) Summary: ThinBackupRestorefails,logsaysCould Supportofsymboliclinkswhichare not restore.Aborting. donebyjenkins Priority: Major Minor 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] [thinBackup] (JENKINS-23377) cron driven backups never happen
Thomas Fürer commented on JENKINS-23377 cron driven backups never happen hi John, It would be nice if you could also send me your settings for thin-backup. and a list of installed plugins. I will try to look into this problem soon. 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] [thinBackup] (JENKINS-22192) Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed
Thomas Fürer updated JENKINS-22192 Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed reduced priority because a siple workaround is in lace - move backup path to a local destination. also a different post shows that the problem must be a configuration thing and not a programming error. Change By: Thomas Fürer (10/Jun/14 4:04 PM) Priority: Blocker Minor 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] [thinBackup] (JENKINS-23377) cron driven backups never happen
Thomas Fürer commented on JENKINS-23377 cron driven backups never happen I've tested it with 1.559 right now and it works for me on a windows 7 machine and also on a ubuntu 14.04 linux box. please add more information about the problem. Add a new log recorder with "hudson.plugins.thinbackup" and a detailed log level. add the logs to this issue. 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] [thinBackup] (JENKINS-22192) Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed
Thomas Fürer commented on JENKINS-22192 Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed sorry for the missunderstanding, but BACKUP_PATH is not an environment variable nor a property. The only way how the backup path could be defined is to use the settings page. I'm not an expert with iscsi, but i think it must be something with the permissions or something else on system level. I do not have any possibility to test with iscsi, but with SMB and NFS it works fine for me. Have you tried to switch the user or extand the permissions to the directory? 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] [thinBackup] (JENKINS-22192) Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed
Thomas Fürer commented on JENKINS-22192 Wrong Error: SEVERE: Could not create backup directory. Backup cannot be performed my configuration JENKINS_HOME=/var/local/jenkins BACKUP_PATH=/home/backup jenkins is runned with the jenkins user (system user without login permission) BACKUP_PATH owner is set to jenkins:jenkins and has r/w/x permissions, r for all others OS: Ubuntu Server 1310 JENKINS: 1.532.1 LTS ThinBackup: 1.7.4 in this configuration I cannot found a problem, I also have test configurations on windows and other linux systems but do not get this error. 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] [thinBackup] (JENKINS-20395) Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server
Thomas Fürer commented on JENKINS-20395 Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server is it possible that you are running out of memory? On linux the behaviour of the JVM is exactly that way you described when it allocates more memory than physical memory is available. So may be you have the do big Xmx value for your JVM and system. You could disable compressing the archives in case you do not have enouph memory, or you have the option to reduce the things you add to the backup (e.g. disable to backup the archive). To be honest I do not work with a Amazone S3 backup so I havn't test it, but I do not think that this migde be an issue. 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] [thinBackup] (JENKINS-21221) Add option for backing up of plugin archives, as well as arbitrary files
Thomas Fürer commented on JENKINS-21221 Add option for backing up of plugin archives, as well as arbitrary files UNSTABLE: Integrated in thinBackup #91 JENKINS-21221: Add option for backing up of plugin archives, as well as arbitrary files. (pmatignon: e33602363860377849015bbb1939f604304813a9) src/main/webapp/help/help-backupAdditionalFiles.html src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink.java src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPluginImpl.java src/main/webapp/help/help-backupPlugins.html src/main/resources/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink/backupsettings.jelly 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] [thinBackup] (JENKINS-21262) Allow Restore of Individual Jenkins Job Configs
Thomas Fürer updated JENKINS-21262 Allow Restore of Individual Jenkins Job Configs thanks Stan, I also have think about this feature, and it will be part of the next big major release thinbackup2.x. stay tuned, I'm still working on it but of course it will take some time to release it. Change By: Thomas Fürer (08/Jan/14 5:28 PM) Issue Type: Bug NewFeature 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] [thinBackup] (JENKINS-21221) Add option for backing up of plugin archives, as well as arbitrary files
Thomas Fürer commented on JENKINS-21221 Add option for backing up of plugin archives, as well as arbitrary files What's wrong with the idea to save only the meta data of the plugins and download/install it during restore operation? Why do you want to save data which already stored in the internet. Don't get me wrong I only want to understand your usecase, because I'm currently working an thinbackup 2.0 with several improvements. 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] [thinBackup] (JENKINS-21221) Add option for backing up of plugin archives, as well as arbitrary files
Thomas Fürer commented on JENKINS-21221 Add option for backing up of plugin archives, as well as arbitrary files thanks for your answee and of course for your work too. I will include your thoughts in my work of a future version of thinbackup 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] [thinBackup] (JENKINS-20837) Differential backups should not cause Jenkins to stop running new jobs
Thomas Fürer commented on JENKINS-20837 Differential backups should not cause Jenkins to stop running new jobs thank you for your realy detailed description. i will take care about when I implement thin-backup 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/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-20868) REST API to control backups
Thomas Fürer commented on JENKINS-20868 REST API to control backups thank you, I will take casre about when implementing thinbackup 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/groups/opt_out.
[JIRA] [core] (JENKINS-20809) JVM Crash during startup
Thomas Fürer created JENKINS-20809 JVM Crash during startup Issue Type: Bug Assignee: Unassigned Attachments: hs_err_pid3524.log, hs_err_pid3688.log Components: core Created: 28/Nov/13 6:33 PM Description: During startup with the built-in jetty the jvm crashes with the following message: Running from: C:\Users\tom\Downloads\jenkins.war webroot: $user.home/.jenkins Nov 28, 2013 7:19:49 PM org.eclipse.jetty.util.log.JavaUtilLog info Information: jetty-8.y.z-SNAPSHOT Nov 28, 2013 7:19:51 PM org.eclipse.jetty.util.log.JavaUtilLog info Information: Extract jar:file:/C:/Users/tom/Downloads/jenkins.war!/ to C:\Users\ tom\AppData\Local\Temp\jetty-0.0.0.0-8080-jenkins.war-any\webapp Nov 28, 2013 7:20:05 PM org.eclipse.jetty.util.log.JavaUtilLog info Information: NO JSP Support for , did not find org.apache.jasper.servlet.JspServ let Jenkins home directory: C:\Users\tom\.jenkins found at: $user.home/.jenkins Nov 28, 2013 7:20:06 PM org.eclipse.jetty.util.log.JavaUtilLog info Information: Started SelectChannelConnector@0.0.0.0:8080 Nov 28, 2013 7:20:06 PM winstone.Logger logInternal Information: Winstone Servlet Engine v2.0 running: controlPort=disabled Nov 28, 2013 7:20:06 PM jenkins.InitReactorRunner$1 onAttained Information: Started initialization Nov 28, 2013 7:20:59 PM jenkins.InitReactorRunner$1 onAttained Information: Listed all plugins Nov 28, 2013 7:20:59 PM jenkins.InitReactorRunner$1 onAttained Information: Prepared all plugins Nov 28, 2013 7:21:00 PM jenkins.InitReactorRunner$1 onAttained Information: Started all plugins Nov 28, 2013 7:21:00 PM jenkins.InitReactorRunner$1 onAttained Information: Augmented all extensions Nov 28, 2013 7:21:00 PM jenkins.InitReactorRunner$1 onAttained Information: Loaded all jobs # A fatal error has been detected by the Java Runtime Environment: # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x77cd2f15, pid=3524, t id=900 # JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18) Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode windows-amd64 compressed oops) Problematic frame: C ntdll.dll+0x52f15 # Failed to write core dump. Minidumps are not enabled by default on client vers ions of Windows # An error report file with more information is saved as: C:\Users\tom\Downloads\hs_err_pid3524.log # If you would like to submit a bug report, please visit: http://bugreport.sun.com/bugreport/crash.jsp The crash happened outside the Java Virtual Machine in native code. See problematic frame for where to report the bug. # C:\Users\tom\Downloads Environment: jenkins: 1.540, 1.541 (clean environment, no workspace present) JRE/JDK: 1.7.0_40 (32/64bit) / 1.7.0_45 (64bit) Windows7 Home (latest updates) installed MS VStudio 2013 Express (c++ Runtime libs 2012/2010/2008) Project: Jenkins Labels: jenkins windows Priority: Critical Reporter: Thomas Fürer 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] [core] (JENKINS-20809) JVM Crash during startup
Thomas Fürer commented on JENKINS-20809 JVM Crash during startup It seems the KernelUtil do not work anymore maybe a new c++ runtime lib have a changed API 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] [build-pipeline] (JENKINS-14565) Please add support for Cloudbees folder structure
Thomas Fürer commented on JENKINS-14565 Please add support for Cloudbees folder structure I have still the problem to setup a build pipeline with jobs placed in folders. I uses the full path as Billy descibes but I fail. 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] [thinBackup] (JENKINS-20761) Trigger Jenkins job after backup
Thomas Fürer commented on JENKINS-20761 Trigger Jenkins job after backup nice idea, i will think about it for version 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/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-20395) Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server
Thomas Fürer commented on JENKINS-20395 Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server thanks for the update, is the corrupt file a 0 byte file? my own jenkins running on ubuntu 13.10 and jenkins 1.531 is working fine, i will try to test the system with java 1.6.x now. curretnly I cannot reproduce 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] [thinBackup] (JENKINS-20547) ThinBackup Restore fails, log says Could not restore. Aborting.
Thomas Fürer updated JENKINS-20547 ThinBackup Restore fails, log says Could not restore. Aborting. changed to new feature, because the usecase is to link parts of the home directory Change By: Thomas Fürer (14/Nov/13 5:40 PM) Issue Type: Bug NewFeature 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] [thinBackup] (JENKINS-20547) ThinBackup Restore fails, log says Could not restore. Aborting.
Thomas Fürer commented on JENKINS-20547 ThinBackup Restore fails, log says Could not restore. Aborting. thank you chris, this is the problem, it will not support links. can you explain my why you have the job configuration out of the home directory? 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] [thinBackup] (JENKINS-20395) Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server
Thomas Fürer commented on JENKINS-20395 Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server could you extract the zip manually? If the zip file itself is the problem please remove it. Where is the file located (network mount, local hdd, local usb mount, raid)? duplicity copies backups to another location, is it possible that this process modifies the file, maybe something gona wrong during sync. The problem is I handled the this case, this is why the Warning is logged, I don't know why the JVM crashes. Have you a crash dump of the JVM? maybe upgrading the JRE to the latest 1.7.0 will help. 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] [thinBackup] (JENKINS-20547) ThinBackup Restore fails, log says Could not restore. Aborting.
Thomas Fürer commented on JENKINS-20547 ThinBackup Restore fails, log says Could not restore. Aborting. is just one backupset which causes this error? 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] [thinBackup] (JENKINS-20547) ThinBackup Restore fails, log says Could not restore. Aborting.
Thomas Fürer edited a comment on JENKINS-20547 ThinBackup Restore fails, log says Could not restore. Aborting. is just one backupset which causes this error? Are there any processes rsync, backup, .. which accesses this file? Where is the backup set located (network mount, local, usb, raid, ...)? 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer commented on JENKINS-17475 Backup stops when processing some file like latestfailedbuild just released 1.7.3, which ignores the symlinks for now; this will result in some unnormal situations for the job history aslong no new build is done. I will try to fix this as soon I have a solution for all the symlink problems with java 1.6 and the different operating systems. I found a lot of different behaivors by changing the jenkins version, the JRE jenkins runs with, and of course the operating system. 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] [thinBackup] (JENKINS-8606) ThinBackup only backs one job out of 10, and continually runs in the background
Thomas Fürer resolved JENKINS-8606 as Fixed ThinBackup only backs one job out of 10, and continually runs in the background Hi bob, this is not related to the original issue, which is fixed. the newer problem is related to https://issues.jenkins-ci.org/browse/JENKINS-17475, which I'm currently working on. So please vote for JENKINS-17475 where I close this issue. Change By: Thomas Fürer (17/Jul/13 4:22 PM) Status: Reopened 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] [thinBackup] (JENKINS-18757) Notify user when backup is done, or provide the option of restarting Jenkins after backup
Thomas Fürer commented on JENKINS-18757 Notify user when backup is done, or provide the option of restarting Jenkins after backup Thank you for your input, I will think about it and do a priorization. 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-13660) JSON fix for Opera in prototype.js probably not good anymore
Thomas Fürer closed JENKINS-13660 as Cannot Reproduce JSON fix for Opera in prototype.js probably not good anymore cannot be reproduced - environment not available anymore Change By: Thomas Fürer (15/Jul/13 6:44 PM) Status: Resolved Closed 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] [thinBackup] (JENKINS-15681) Support for Cloudbees Folders
Thomas Fürer assigned JENKINS-15681 to Ruben Perez Support for Cloudbees Folders Please verify and close it. thx Change By: Thomas Fürer (15/Jul/13 6:46 PM) Assignee: ThomasFürer RubenPerez 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] [thinBackup] (JENKINS-18093) thinBackup stops if there's no unstable build
Thomas Fürer resolved JENKINS-18093 as Duplicate thinBackup stops if theres no unstable build Change By: Thomas Fürer (14/Jun/13 2:54 PM) 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] [sctmexecutor] (JENKINS-17922) SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 (
Thomas Fürer commented on JENKINS-17922 SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 ( sorry JJ for the delay, i missed the notification about this issue. Unfortunately I have no access to any SCTM system since some time, so it would be hard to test it. Let me see if I can do something for you. 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] [sctmexecutor] (JENKINS-17922) SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 (
Thomas Fürer commented on JENKINS-17922 SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 ( BTW: Because of limited time I'm not able to support hudson, so please consider switching your system to jenkins. Otherwise you need to wait until I have some time to look at it, or fix it for you own. If you have questions about the plug-in implementation I can probably give you an answer, but SCTM related questions I need to direct to the community page of borland.com. 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] [sctmexecutor] (JENKINS-17922) SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 (
Thomas Fürer commented on JENKINS-17922 SCTM Executor plugin Class loading issue when running jenkins on JBoss AS 5 ( In reply to comment #1: sorry JJ for the delay, i missed the notification about this issue. Unfortunately I have no access to any SCTM system since some time, so it would be hard to test it. Let me see if I can do something for you. sorry my fault, sebastian is already assigned, so it would be good to wait for his response. I'm a little bit confused. + Have you a running jenkins or a hudson (because of the different environment specification and the documentation link)? 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-17822) TestResults are listed twice
Thomas Fürer created JENKINS-17822 TestResults are listed twice Issue Type: Bug Assignee: Unassigned Attachments: doubledTestResult.PNG Components: core, junit Created: 02/May/13 7:05 AM Description: I have a maven pom project to execute integration tests (using the smartbear SoapUI Runner). This runner produces valid junit results (no duplicates, in xml, txt and also html). the problem now is that some (not all) of the testcases are listed twice. It is not relevant if the test fails or a OK. Only the first occurence in the list (failed tests) is clickable (). I checked the xml again and there are no duplicates. Also the testcount is strange Total count in jenkins is 970 but actually I have only 485 testcases. Environment: OS: Master - Windows, Slave - Suse Linux Jenkins ver. 1.496 Project: Jenkins Priority: Major Reporter: Thomas Fürer 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-13660) JSON fix for Opera in prototype.js probably not good anymore
Thomas Fürer resolved JENKINS-13660 as Cannot Reproduce JSON fix for Opera in prototype.js probably not good anymore Sorry, but I cannot reproduce it because the environment is not available anymore. I will close it (as "Cannot Reproduce"). If it is still a problem for someone, he will enter a new issue anyways. Change By: Thomas Fürer (01/May/13 6:38 PM) Status: Open Resolved Resolution: CannotReproduce 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer commented on JENKINS-17475 Backup stops when processing some file like latestfailedbuild unfortently the fix I have done is not working on all supported OS and also I have to search for some compatibility mode to older jenkins versions than 1.507. therfore it takes a little bit longer to fix this problem. stay tuned I'm working on 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer created JENKINS-17475 Backup stops when processing some file like latestfailedbuild Issue Type: Bug Assignee: Thomas Fürer Components: thinBackup Created: 04/Apr/13 4:46 PM Description: 03.04.2013 09:13:04 org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SCHWERWIEGEND: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path 'C:\CIServer\Backup\'. java.io.IOException: Source 'C:\Program Files (x86)\Jenkins\jobs\Bank Trunk\builds\lastFailedBuild' exists but is not a directory at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:869) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildFiles(HudsonBackup.java:302) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildsFor(HudsonBackup.java:270) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:208) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:196) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:175) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:142) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink$1.execute(ThinBackupMgmtLink.java:76) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Unknown Source) 03.04.2013 09:12:40 org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup backupJobsDirectory INFO: Found 63 jobs to back up. 03.04.2013 09:12:40 org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink doBackupManual INFO: Starting manual backup. Indeed, lastFailedBuild is a normal file and not a directory. Since Jenkins 1.507 there are these special files (see http://jenkins-ci.org/changelog). Do you think you can address this issue quickly? Environment: Jenkins since 1.507 (reproduced on 1.509) thinBackup 1.7.2 Project: Jenkins Priority: Blocker Reporter: Thomas Fürer 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer started work on JENKINS-17475 Backup stops when processing some file like latestfailedbuild Change By: Thomas Fürer (04/Apr/13 6:26 PM) Status: Open InProgress 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] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer commented on JENKINS-17475 Backup stops when processing some file like latestfailedbuild Integrated in thinBackup #80 JENKINS-17475: add new files in the builds folder to the backup archive (Revision 9dd19dfccf35fb323e9dd34eb7d40ff672f47070) Result = SUCCESS tfuerer.javanet : 9dd19dfccf35fb323e9dd34eb7d40ff672f47070 Files : pom.xml src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/main/java/org/jvnet/hudson/plugins/thinbackup/restore/PluginRestoreUpdateCenter.java 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] (JENKINS-17166) Counting in the Test Trend Chart differs to the number of tests in the Grid
Thomas Fürer created JENKINS-17166 Counting in the Test Trend Chart differs to the number of tests in the Grid Issue Type: Bug Assignee: Peter Hayes Attachments: countingFailure.PNG Components: dashboard-view Created: 12/Mar/13 7:26 AM Description: As the screenshot demonstrate, the total count of tests is in my suite 8138 but the Trend Chart shows me more then 9000 tests. Settings: "640x220", "All Tests" in the last "30" days Environment: Jenkins: 1.496 Dashboard-plugin: 2.4 Project: Jenkins Priority: Major Reporter: Thomas Fürer 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] (JENKINS-14062) can we zip ALL the backups and not just the 'old' ones?
Thomas Fürer commented on JENKINS-14062 can we zip ALL the backups and not just the old ones? this is a valid request. I need to find a solution to manage this, because I need an uncompressed version to do the differential backups. Also there are some higher priored issues I need to fix, e.g. more feedback during backup and abortable backup. Please stay tuned. 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] (JENKINS-16897) thinBackup is expecting everything in the jobs folder to be a directory
Thomas Fürer commented on JENKINS-16897 thinBackup is expecting everything in the jobs folder to be a directory just released version 1.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] (JENKINS-16897) thinBackup is expecting everything in the jobs folder to be a directory
Thomas Fürer resolved JENKINS-16897 as Duplicate thinBackup is expecting everything in the jobs folder to be a directory https://issues.jenkins-ci.org/browse/JENKINS-16426 Change By: Thomas Fürer (20/Feb/13 8:20 PM) 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] (JENKINS-16897) thinBackup is expecting everything in the jobs folder to be a directory
Thomas Fürer commented on JENKINS-16897 thinBackup is expecting everything in the jobs folder to be a directory Hi paul, please look at the already fixed issue. if it is okay for you how I fixed it I would release a new version shortly. 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] (JENKINS-16609) Backup buuild results/artifacts only for Keep this build forever marked builds
Thomas Fürer created JENKINS-16609 Backup buuild results/artifacts only for Keep this build forever marked builds Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 02/Feb/13 9:07 AM Description: original ask by rjnichols and finally also implemented by himself Project: Jenkins Priority: Major Reporter: Thomas Fürer 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] (JENKINS-16609) Backup build results/artifacts only for Keep this build forever marked builds
Thomas Fürer updated JENKINS-16609 Backup build results/artifacts only for Keep this build forever marked builds Change By: Thomas Fürer (02/Feb/13 9:08 AM) Summary: Backup buuild build results/artifactsonlyforKeepthisbuildforevermarkedbuilds Description: original ask asked byrjnicholsandfinallyalsoimplementedbyhimself 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] (JENKINS-16609) Backup build results/artifacts only for Keep this build forever marked builds
Thomas Fürer resolved JENKINS-16609 as Fixed Backup build results/artifacts only for Keep this build forever marked builds Change By: Thomas Fürer (02/Feb/13 9:11 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] (JENKINS-16489) Current thinBackup doesn't copy build artifacts from sub-folders
Thomas Fürer created JENKINS-16489 Current thinBackup doesnt copy build artifacts from sub-folders Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 25/Jan/13 3:22 PM Description: by Richard Nichols: This occurs in multi-module Maven projects with manual artifact archiving. I have changed the filter to also include sub-folders for build artifacts. Project: Jenkins Priority: Major Reporter: Thomas Fürer 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
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Thomas Fürer resolved JENKINS-16426 as Fixed Backup fails while copying a file from the jobs folder problem is fix and workaround for special case is to move files to the userContent folder. if this is still a problem for you do not hesitate to reopen this issue. Than I will implement the inclution of these files. Change By: Thomas Fürer (25/Jan/13 4:04 PM) 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
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Thomas Fürer commented on JENKINS-16426 Backup fails while copying a file from the jobs folder There is no special reason why I would not include files in the job directory to the back up. The idea of thinBackup is to back up only a minimum set of configuration to keep it small and handy. As normally the jobs folder is under control of jenkins. I never would put files in this folder by my own. However, you have done it. I suggest to put the configurations under JENKINS_HOME (where all other global configurations are placed), alternativly I would suggest the userContent folder. Including files in the job folder to the backup will also open the question why not include files in other jenkins controlled folders. So this will open a neverending task because several plugins (e.g. CloudBees Folders or Matrix Job Configuration) will have their own folder structure, which makes it complicated to back up only a minimal set of files. Is, moving the files to the suggested folders, an option for you? If not I need to refactor some code and redefine some ideas, technical it is possible, but I'm not sure if I should do it at the moment. 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
[JIRA] (JENKINS-16434) thinBackup plugin puts Jenkins into shutdown mode and does not come out of it
Thomas Fürer commented on JENKINS-16434 thinBackup plugin puts Jenkins into shutdown mode and does not come out of it as a quickfix we should work on JENKINS-15771; to fix the essential problem (deadlock) we need findout more about the running job to detect the deadlock. 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
[JIRA] (JENKINS-16434) thinBackup plugin puts Jenkins into shutdown mode and does not come out of it
Thomas Fürer edited a comment on JENKINS-16434 thinBackup plugin puts Jenkins into shutdown mode and does not come out of it as a quickfix we should work on JENKINS-15771; to fix the essential problem (deadlock) we need to findout more about the running job to detect the deadlock. 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
[JIRA] (JENKINS-16426) Backup fails while copying a file from the jobs folder
Thomas Fürer commented on JENKINS-16426 Backup fails while copying a file from the jobs folder Why do you have a xml file in the jobs directory. normally there are only folders in there. can you please tell me which plugins you use and which of it will store files in the jobs directory, or why this file is placed in this 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
[JIRA] (JENKINS-11346) Multi-Configuration Jobs remember deleted slaves
Thomas Fürer closed JENKINS-11346 as Cannot Reproduce Multi-Configuration Jobs remember deleted slaves Change By: Thomas Fürer (20/Jan/13 8:52 AM) Status: Resolved Closed 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
[JIRA] (JENKINS-11346) Multi-Configuration Jobs remember deleted slaves
Thomas Fürer commented on JENKINS-11346 Multi-Configuration Jobs remember deleted slaves I cannot reproduce it because I do not have access to this environment anymore, sorry maybe you should close 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
[JIRA] (JENKINS-15681) Support for Cloudbees Folders
Thomas Fürer resolved JENKINS-15681 as Fixed Support for Cloudbees Folders Change By: Thomas Fürer (08/Dec/12 5:21 PM) 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
[JIRA] (JENKINS-15681) Support for Cloudbees Folders
Thomas Fürer commented on JENKINS-15681 Support for Cloudbees Folders add cloudbees folder support 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
[JIRA] (JENKINS-6956) NPE if Buildsnumbers are not configured wrong
Thomas Fürer resolved JENKINS-6956 as Fixed NPE if Buildsnumbers are not configured wrong Change By: Thomas Fürer (08/Dec/12 6:23 PM) 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
[JIRA] (JENKINS-10947) Can full backups include the plugins folder?
Thomas Fürer stopped work on JENKINS-10947 Can full backups include the plugins folder? Change By: Thomas Fürer (09/Nov/12 12:45 PM) Status: InProgress Open 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
[JIRA] (JENKINS-10947) Can full backups include the plugins folder?
Thomas Fürer resolved JENKINS-10947 as Fixed Can full backups include the plugins folder? will be released with the next version Change By: Thomas Fürer (09/Nov/12 12:45 PM) 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
[JIRA] (JENKINS-15771) Backup Process schould be abortable manually
Thomas Fürer created JENKINS-15771 Backup Process schould be abortable manually Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 08/Nov/12 2:47 PM Description: If something is wrong with the backup, it could be that the backup hangs, or some action must be executed very urgent but the backup process blocks it. cancling the quiet-mode caused a new start of the backup proccess. it would be good have the possibility to cancle the whole backup. Project: Jenkins Priority: Major Reporter: Thomas Fürer 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
[JIRA] (JENKINS-15681) Support for Cloudbees Folders
Thomas Fürer commented on JENKINS-15681 Support for Cloudbees Folders Hi Ruben, Is it possible to send me a schematic directory layout of the workspace filesystem, so I can estimate what this means to thinBackup? I'm sure it would be only a little change, but just to be sure. 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
[JIRA] (JENKINS-15099) Max number of backup sets ignored
Thomas Fürer updated JENKINS-15099 Max number of backup sets ignored Change By: Thomas Fürer (01/Nov/12 11:04 AM) Status: Reopened Open 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
[JIRA] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Thomas Fürer updated JENKINS-12096 ThinBackup Worker Thread thread is still running. Execution aborted. Change By: Thomas Fürer (01/Nov/12 11:53 AM) Status: Reopened Open 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
[JIRA] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Thomas Fürer resolved JENKINS-12096 as Cannot Reproduce ThinBackup Worker Thread thread is still running. Execution aborted. cannot reproduce this issue. Only if the backup is already/still running and a new backup will be trigger this happens. But I don't think that some have such a tight schedule. The other thing is that something on the filesystem could block the backup. In this case you should watch out for permission settings or parallel file operations. in all this cases I cannot handle the issue in the backup plugin, so I decided to close this one. Change By: Thomas Fürer (01/Nov/12 11:57 AM) Status: Open Resolved Resolution: CannotReproduce 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
[JIRA] (JENKINS-15514) Backup 'userContents' folder is missing help
Thomas Fürer resolved JENKINS-15514 as Fixed Backup userContents folder is missing help Change By: Thomas Fürer (13/Oct/12 7:36 AM) Status: InProgress 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
[JIRA] (JENKINS-15514) Backup 'userContents' folder is missing help
Thomas Fürer commented on JENKINS-15514 Backup userContents folder is missing help fix will be part of the next release (probably 1.7) Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15099) Max number of backup sets ignored
Thomas Fürer commented on JENKINS-15099 Max number of backup sets ignored Oliver, Which user runs jenkins? Has this user access rights to this directory? Have you tried the same with a directory without space? I'm not sure if this is the issue because I just tested it on my Kubuntu 12.04 with a directory with a space in it and I have no problem with it. If you use Tomcat as servlet container you should look at this https://wiki.jenkins-ci.org/display/JENKINS/Tomcat. Maybe the URIEncoding takes also effect to this issue. 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
[JIRA] (JENKINS-15099) Max number of backup sets ignored
Thomas Fürer commented on JENKINS-15099 Max number of backup sets ignored okay, can you tell me which encoding your system is using. Please try to look into your jenkins_home, there will be a thinbackup.xml. Please check if the encoding of the backuppath is correct in this file. 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
[JIRA] (JENKINS-15099) Max number of backup sets ignored
Thomas Fürer resolved JENKINS-15099 as Cannot Reproduce Max number of backup sets ignored tested with windows 7 and kubuntu 12.04 / ubuntu server 12.04 with the latest jenkins and thinbackup plugin available on the update server. everything works as expected. Change By: Thomas Fürer (10/Sep/12 4:57 PM) Status: Open Resolved Resolution: CannotReproduce 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
[JIRA] (JENKINS-14647) VMs will be started until a job is waiting in the queue
Thomas Fürer created JENKINS-14647 VMs will be started until a job is waiting in the queue Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud Created: 01/Aug/12 6:55 AM Description: I have several ESXi instances in my environment with VMs on it which I need only for testing. I have also several jobs which triggers the tests. because I have very different technologies and because I do not want to maintain all VMs with all technologies I have labeled the VMs and also the jobs. So some jobs can be executed everywhere, some others only on specific VMs. The problem is that a waiting job in the queue triggers the deployment of all VMs currently not in use. If the job cannot be executed on these VMs a loop of deploying and undeploying VMs will be triggered until the job will be handled by an executor. Suggestion for a solution: Before a VM gets deployed it should be checked if the labels will allow an execution on this executor. Environment: jenkins 1.466, vsphere-cloud 0.10, several esxi instances Project: Jenkins Priority: Major Reporter: Thomas Fürer 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
[JIRA] (JENKINS-14288) thinBackup doesn't put back the current shutdown flag after backing up
Thomas Fürer commented on JENKINS-14288 thinBackup doesnt put back the current shutdown flag after backing up I'm a bit confused. Please correct me if I am wrong. Your problem is that jenkins is set to shutdown not via thinbackup but some mechanism outside of thinbackup (e.g. manually, as you describted in your last post), and you would have jenkins still be in shutdown also after a successful backup. Am I 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
[JIRA] (JENKINS-14288) thinBackup doesn't put back the current shutdown flag after backing up
Thomas Fürer started work on JENKINS-14288 thinBackup doesnt put back the current shutdown flag after backing up Change By: Thomas Fürer (25/Jul/12 8:33 AM) Status: Open InProgress 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
[JIRA] (JENKINS-14288) thinBackup doesn't put back the current shutdown flag after backing up
Thomas Fürer resolved JENKINS-14288 as Fixed thinBackup doesnt put back the current shutdown flag after backing up Change By: Thomas Fürer (25/Jul/12 8:49 AM) Status: InProgress 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
[JIRA] (JENKINS-14288) thinBackup doesn't put back the current shutdown flag after backing up
Thomas Fürer commented on JENKINS-14288 thinBackup doesnt put back the current shutdown flag after backing up In reply to comment #5: That's correct. sorry for the delay. I was simply confused, but it was a simple fix. I just committed a change. I will also try to push a new release but I need to do some testing before. so please hold on. thomas 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
[JIRA] (JENKINS-12098) FileNotFoundException causes backup process to terminate
Thomas Fürer resolved JENKINS-12098 as Fixed FileNotFoundException causes backup process to terminate Change By: Thomas Fürer (25/Jul/12 10:41 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
[JIRA] (JENKINS-12173) thinBackup does not include build results for matrix projects when nodes axis is used
Thomas Fürer started work on JENKINS-12173 thinBackup does not include build results for matrix projects when nodes axis is used Change By: Thomas Fürer (25/Jul/12 11:45 AM) Status: Open InProgress 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
[JIRA] (JENKINS-12173) thinBackup does not include build results for matrix projects when nodes axis is used
Thomas Fürer commented on JENKINS-12173 thinBackup does not include build results for matrix projects when nodes axis is used Integrated in thinBackup #47 JENKINS-12173: thinBackup does not include build results for matrix projects when nodes axis is used (Revision 40679) Result = FAILURE tofuatjava : 40679 Files : /trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java /trunk/hudson/plugins/thinBackup/src/test/java/org/jvnet/hudson/plugins/thinbackup/HudsonDirectoryStructureSetup.java /trunk/hudson/plugins/thinBackup/src/test/java/org/jvnet/hudson/plugins/thinbackup/TestHelper.java /trunk/hudson/plugins/thinBackup/src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestBackupMatrixJob.java /trunk/hudson/plugins/thinBackup/src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestBackupZipping.java /trunk/hudson/plugins/thinBackup/src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestHudsonBackup.java /trunk/hudson/plugins/thinBackup/src/test/java/org/jvnet/hudson/plugins/thinbackup/restore/TestHudsonRestore.java 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
[JIRA] (JENKINS-14288) thinBackup doesn't put back the current shutdown flag after backing up
Thomas Fürer commented on JENKINS-14288 thinBackup doesnt put back the current shutdown flag after backing up Integrated in thinBackup #47 JENKINS-14288: thinBackup doesn't put back the current shutdown flag after backing up (Revision 40678) Result = FAILURE tofuatjava : 40678 Files : /trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPeriodicWork.java /trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/utils/Utils.java 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
[JIRA] (JENKINS-13980) The archive folder gets lost if you also backup archives for builds
Thomas Fürer commented on JENKINS-13980 The archive folder gets lost if you also backup archives for builds Integrated in thinBackup #47 JENKINS-13980: archives will be back-uped for the differential back-up only if changes are detected (like all other files) (Revision 40624) JENKINS-13980: fix missing archive folder but the archive gets backuped also for each DIFF regardless if the archive was changed (Revision 40623) Result = FAILURE tofuatjava : 40624 Files : /trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java alienllama : 40623 Files : /trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java 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
[JIRA] (JENKINS-14288) thinBackup doesn't put back the current shutdown flag after backing up
Thomas Fürer commented on JENKINS-14288 thinBackup doesnt put back the current shutdown flag after backing up Integrated in thinBackup #50 JENKINS-14288: thinBackup doesn't put back the current shutdown flag after backing up (Revision 40678) Result = FAILURE tofuatjava : 40678 Files : /trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPeriodicWork.java /trunk/hudson/plugins/thinBackup/src/main/java/org/jvnet/hudson/plugins/thinbackup/utils/Utils.java 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
