[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani resolved JENKINS-17885 as Fixed Publish over SSH lost main configuration data after jenkins server reboot Fixed in version 1.11 of the Publish over SSH plugin. Change By: Mark Ottaviani (06/Jan/14 3:14 PM) Status: Open Resolved Assignee: bap wearbif 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Email from bap: Hi Mark, I no longer use Jenkins and don't have time to maintain the publish over plugins. Feel free to merge, test and release as you see fit. Regards, Bap. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Alexander Fischer commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Hello, how can we take over the maintainance for the plugins? I use my own patched version (see on Github) for a long-time without any problems. https://github.com/afischer211/publish-over-plugin https://github.com/afischer211/publish-over-ssh-plugin Is Github the correct place for Jenkins-plugins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Tom Fanning commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot A pull request for this same bug manifested in the Publish over CIFS plugin was merged 2 months ago: https://github.com/jenkinsci/publish-over-cifs-plugin/pull/1 The updated plugin got built here: https://jenkins.ci.cloudbees.com/job/plugins/job/publish-over-cifs-plugin/4/org.jenkins-ci.plugins$publish-over-cifs/ I removed the CIFS plugin installed in Jenkins and manually installed that one, and it works fine. Bug fixed (CIFS plugin). Not sure whether the version appearing on the plugin feed is fixed too. There is a similar pull request for this bug against the Publish over SSH plugin here: https://github.com/jenkinsci/publish-over-ssh-plugin/pull/4 I guess we need to get that pull request merged as well. No idea how to proceed from here. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Tom Fanning edited a comment on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot A pull request for this same bug manifested in the Publish over CIFS plugin was merged 2 months ago: https://github.com/jenkinsci/publish-over-cifs-plugin/pull/1 The updated plugin got built here: https://jenkins.ci.cloudbees.com/job/plugins/job/publish-over-cifs-plugin/4/org.jenkins-ci.plugins$publish-over-cifs/ I removed the CIFS plugin installed in Jenkins and manually installed that one, and it works fine. Bug fixed (CIFS plugin). Not sure whether the version appearing on the plugin feed is fixed too. There is a similar pull request for this bug against the Publish over SSH plugin here: https://github.com/jenkinsci/publish-over-ssh-plugin/pull/4 I guess we need to get that pull request merged as well. No idea how to proceed from here. There is also some activity here: https://issues.jenkins-ci.org/browse/JENKINS-17058?focusedCommentId=177125page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-177125 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot I've e-mailed the listed committers and maintainers for this plugin to see if we can get the pull request moving. If that doesn't work I'll work through this with Cloudbees directly. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
François Dumont commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Does Hudson have the same issue? Thinking of trying something new 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot There does appear to be a pending pull request: JENKINS-17885 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani edited a comment on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Looking forward to seeing this fixed. Same 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jurica Krizanic commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Still occurs, Jenkins 1.540, Publish over SSH plugin 1.10 ! 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jon Starbird commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot PLEASE FIX THIS ISSUE. This plugin could be very valuable but with this bug it is completely useless. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Eric Stob commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Same issue in Windows. The bug renders the plugin completely useless. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Eric Stob updated JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Change By: Eric Stob (25/Jul/13 7:51 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jan Krotký
commented on JENKINS-17885
Publish over SSH lost main configuration data after jenkins server reboot
Confirming same XLM load error as in CiFS issue. Strange is, that the publish over FTP plugin (which on the quick overlook uses similar configuration) is not affected.
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141]: org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad: defining beans [authenticationManager]; root of factory hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca]: org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc: defining beans [filter,legacy]; root of factory hierarchy
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
couldn't setup local SOCKS5 proxy on port : Address already in use
Running from: /usr/lib/jenkins/jenkins.war
22.7.2013 10:27:50 winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: System.getProperty("JENKINS_HOME")
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: HTTP Listener started: port=8080
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: AJP13 Listener started: port=8009
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
22.7.2013 10:27:55 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:27:56 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:27:57 hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run
INFO: Trying to connect
22.7.2013 10:27:57 hudson.plugins.im.HudsonIsBusyListener init
INFO: Executor busy listener created
22.7.2013 10:27:58 org.jenkinsci.plugins.scriptler.ScritplerPluginImpl synchronizeConfig
INFO: initialize scriptler
22.7.2013 10:28:01 hudson.plugins.greenballs.PluginImpl start
INFO: Green Balls!
22.7.2013 10:28:05 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:28:14 hudson.model.Descriptor load
WARNING: Failed to load /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
hudson.util.IOException2: Unable to read /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
at
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Jan Krotký
edited a comment on JENKINS-17885
Publish over SSH lost main configuration data after jenkins server reboot
Confirming same XML load error as in CiFS issue. Strange is, that the publish over FTP plugin (which on the quick overlook uses similar configuration) is not affected.
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
22.7.2013 10:22:27 jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
22.7.2013 10:22:28 jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@5f8d0141]: org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@146ae3ad: defining beans [authenticationManager]; root of factory hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca: display name [Root WebApplicationContext]; startup date [Mon Jul 22 10:22:28 CEST 2013]; root of context hierarchy
22.7.2013 10:22:28 org.springframework.web.context.support.StaticWebApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@4fabb0ca]: org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc
22.7.2013 10:22:28 org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
INFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@281edacc: defining beans [filter,legacy]; root of factory hierarchy
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
22.7.2013 10:22:42 org.apache.commons.jexl.util.Introspector clearCache
INFO: Introspector : detected classloader change. Dumping cache.
couldn't setup local SOCKS5 proxy on port : Address already in use
Running from: /usr/lib/jenkins/jenkins.war
22.7.2013 10:27:50 winstone.Logger logInternal
INFO: Beginning extraction from war file
Jenkins home directory: /var/lib/jenkins found at: System.getProperty("JENKINS_HOME")
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: HTTP Listener started: port=8080
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: AJP13 Listener started: port=8009
22.7.2013 10:27:54 winstone.Logger logInternal
INFO: Winstone Servlet Engine v0.9.10 running: controlPort=disabled
22.7.2013 10:27:55 jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
22.7.2013 10:27:56 jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
22.7.2013 10:27:57 hudson.plugins.im.IMConnectionProvider$ConnectorRunnable run
INFO: Trying to connect
22.7.2013 10:27:57 hudson.plugins.im.HudsonIsBusyListener init
INFO: Executor busy listener created
22.7.2013 10:27:58 org.jenkinsci.plugins.scriptler.ScritplerPluginImpl synchronizeConfig
INFO: initialize scriptler
22.7.2013 10:28:01 hudson.plugins.greenballs.PluginImpl start
INFO: Green Balls!
22.7.2013 10:28:05 jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
22.7.2013 10:28:14 hudson.model.Descriptor load
WARNING: Failed to load /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
hudson.util.IOException2: Unable to read /var/lib/jenkins/jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml
at
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
sogabe assigned JENKINS-17885 to bap Publish over SSH lost main configuration data after jenkins server reboot Change By: sogabe (16/Jul/13 1:08 PM) Assignee: bap 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Kerstin Klein commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Jenkins 1.514 installed on Centos 6.3, problem also occurs with Publish Over CiFS. Please fix or provide workaround. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
A AA updated JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Change By: A AA (16/May/13 4:35 PM) Attachment: no_ssh_config.png 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
wearbif updated JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Change By: wearbif (16/May/13 4:42 PM) Description: Afterjenkinsserverreboot,configurationislostonmainoptionsmenu.Buildjobssavepublish-over-sshconfiguaionscorrectly. Ascreenshotshowsaconfiguratingwindowafterreboot. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
A AA created JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Issue Type: Bug Affects Versions: current Assignee: Alex Earl Attachments: config.xml, jenkins.plugins.publish_over_cifs.CifsPublisherPlugin.xml, jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml Components: publish-over-cifs, publish-over-ssh Created: 07/May/13 10:17 AM Description: After jenkins server reboot, configuration is lost on main options menu. Build jobs save publish-over-ssh configuaions correctly, but reference to main data lost. Due Date: 07/May/13 12:00 AM Environment: Jenkins server is running on Windows Server 2008. Jenkins build agent running on Ubuntu 12.04 LTS. Project: Jenkins Labels: jenkins plugin slave configuration Priority: Major Reporter: A AA 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Alex Earl assigned JENKINS-17885 to Unassigned Publish over SSH lost main configuration data after jenkins server reboot Change By: Alex Earl (07/May/13 10:50 AM) Assignee: AlexEarl 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.
