|
||||||||
|
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-15674) Choosing strategy reset... [email protected] (JIRA)
- [JIRA] (JENKINS-15674) Choosing strategy ... [email protected] (JIRA)
- [JIRA] (JENKINS-15674) Choosing strategy ... [email protected] (JIRA)
- [JIRA] (JENKINS-15674) Choosing strategy ... [email protected] (JIRA)

I'm seeing this on Windows 7. Seems more likely to happen, upon Jenkins restart. Not necessarily all restarts (or perhaps only those which truly kill and restart the process/service) – I've seen Jenkins self-restart and not lose the setting.
Really grasping at straws, but Jenkins does sometimes report an issue with inscrutable data, which appears to be related to CVS plugin and passwords. But, we're using git, not CVS, so this may not be related.