Ran into this issue with both Jenkins 1.482 and 1.483. It only happened with one URL (a second test server I ran did not experience the same issue, but it was run on a different box).

At Daniel Latter's advice from the previous comment, clearing the cache seemed to solve the 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

Reply via email to