I can reproduce the exception from Jenkins 1.499 by creating a multi-configuration project and trying to execute Groovy command as a build step. The execution is successful but when trying to access any configuration I get a Status Code:404 page and the system log displays the exception with the stack trace from that issue. Any ideas if it was fixed in the newer versions?

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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to