|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

@cforce,
I will do it now, but it will not be valid test anymore because once I reverted to v1.529, I updated plugins. So it might work now, but it does not cover the issue I had earlier - crash after second reboot ( after plugins update ).
Test scenarion:
1. Up and running jenkins v1.529 with master and three slaves; All slaves offline;![]()
![]()
![]()
![]()
2. Plugins - all updated ( from my last attempt ( see date of my previous comment here ));
3. Creating a slave ; installing as windows service ; starting it - up and running;
3.1 Updating java to 1.7u45 ;
4. Performing automatic upgrade with one job running and one in queue ; waiting till it finishes;
Resulting in error from console before returning
in console:5. Rebooting jenkins;![]()
![]()
6. Updating plugins, if available.
7. Checking result...