We've noticed the same behavior: Jenkins v1.491 since upgrading from 1.484. We found another workaround - hit some page that list the jobs whose builds can't be accessed via direct URL. I suppose we could browse all jobs upon Jenkins startup to ensure this URL jumping behavior works correctly. But it would be much better if it just worked properly.

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