|
||||||||
|
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-15929) Visiting Configure Sys... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)
- [JIRA] (JENKINS-15929) Visiting Configur... [email protected] (JIRA)

Note: This seemed to work quite recently, so it is possible that it is caused by upgrading to Jenkins 1.492 from 1.491