|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Thanks for the IntelliJ primer Justin.
Since we can't support this feature without increasing the minimum supported Jenkins version, is there instead a way that we can query the Jenkins version at runtime and modify the job-dsl-plugin's behaviour? For example, if at runtime I know that we are running in Jenkins 1.456, then the DSL functionality for this feature can throw a meaningful exception, ignore it, or whatever we decide is appropriate. When running in 1.509 or greater it could implement the feature as required.
I think the ability to make decisions at runtime based on the Jenkins version would help allow us to move forward with new features while still maintaining backwards compatibility with older Jenkins versions.