[JIRA] (JENKINS-55344) Allow to run Groovy scripts in JCasC
Title: Message Title Tomasz Szandała commented on JENKINS-55344 Re: Allow to run Groovy scripts in JCasC TBH I have tested this few dozen times and I did not notice aby issues. Could You try? I have made pull requested #687 with proposed feature. So far IT passed my tests... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-53250) Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201)
Title: Message Title Tomasz Szandała commented on JENKINS-53250 Re: Gerrit Trigger plugin compatibility with Jenkins As Code plugin (JEP-201) Paweł Kurek & rsandell: Guys, could You please take a look on my idea for JCasC: https://github.com/jenkinsci/configuration-as-code-plugin/pull/687 It might help You Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
[JIRA] (JENKINS-55344) Allow to run Groovy scripts in JCasC
Title: Message Title Tomasz Szandała created an issue Jenkins / JENKINS-55344 Allow to run Groovy scripts in JCasC Issue Type: New Feature Assignee: Tomasz Szandała Components: configuration-as-code-plugin Created: 2018-12-27 11:09 Priority: Major Reporter: Tomasz Szandała It would be vital to be able to run Groovy script as part of JCasC configuration. First of all there will be always something, that when Yaml is insufficient and can be done only using Groovy. While we can still run Groovy, by putting them in init.groovy.d, it is reasonable to be able to reload them along JCasC configuration Add Comment
