[JIRA] [core] (JENKINS-22175) slave nodes are forgotten
Bernhard Wiedemann updated JENKINS-22175 slave nodes are forgotten Change By: Bernhard Wiedemann (14/Mar/14 1:36 PM) Description: Weexperiencedthat sometimes oneofninejenkinsslave/workernodesisforgotten -mostlyafter onevery jenkinsrestart.Manuallyre-addingnodesagainandagainisverycumbersome-especiallysincethereisnoAPIforthat.Wewouldappreciatehelpfordeeperdebuggingthisissue. 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-22175) slave nodes are forgotten
Bernhard Wiedemann commented on JENKINS-22175 slave nodes are forgotten Further analysis showed that config.xml still contained the missing slave entry, but jenkins consistently ignored the first slave.../slave part for its live data. 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-22175) slave nodes are forgotten
Bernhard Wiedemann created JENKINS-22175 slave nodes are forgotten Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Mar/14 1:54 PM Description: We experienced that sometimes one of nine jenkins slave/worker nodes is forgotten - mostly after jenkins restart. Manually re-adding nodes again and again is very cumbersome - especially since there is no API for that. We would appreciate help for deeper debugging this issue. Project: Jenkins Priority: Major Reporter: Bernhard Wiedemann 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-22175) slave nodes are forgotten
Bernhard Wiedemann updated JENKINS-22175 slave nodes are forgotten Change By: Bernhard Wiedemann (13/Mar/14 2:25 PM) Attachment: SystemInformation[Jenkins].html 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] (JENKINS-7501) POST'ing a config.xml to create a new job via the XML API results in newlines being removed from XML elements containing them (ant build steps, winbatch steps, etc)
Bernhard Wiedemann commented on JENKINS-7501 POSTing a config.xml to create a new job via the XML API results in newlines being removed from XML elements containing them (ant build steps, winbatch steps, etc) still present in Jenkins 1.461 It is breaking backup/restore for us because we have multi-line properties to set multiple shell variables 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
