|
||||||||||||||
|
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/d/optout.
Here script is null in the CpsFlowDefinition, whereas it should be at worst an empty string. But I think this is a red herring. From the screenshot I gather that the configuration of the definition, including the script field, did not appear at all for some reason. Most likely there is some error either in your Jenkins logs or in the browser _javascript_ console which would explain why the configuration form is broken.
Did you try restarting Jenkins after installing the Workflow plugin? Currently some features are known not to work after an initial dynamic install (but I have not heard of this problem).
At any rate, I tried running 1.595 on a fresh $JENKINS_HOME and installing Workflow: Aggregator (which pulls in its dependencies), and was able to configure and save a new flow.