[JIRA] (JENKINS-60209) jCasC-Groovy not expanding variables
Title: Message Title Maciej Wolniewicz commented on JENKINS-60209 Re: jCasC-Groovy not expanding variables Tomasz Szandała are there any estimates when this feature is implemented? It would be great if configuration-as-code-groovy-plugin process the variables the same way as configuration-as-code-plugin does, especially when handling secrets in jenkins helm chart. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203181.1574155542000.21971.1588676340159%40Atlassian.JIRA.
[JIRA] (JENKINS-60209) jCasC-Groovy not expanding variables
Title: Message Title
Cyril Marin created an issue
Jenkins / JENKINS-60209
jCasC-Groovy not expanding variables
Issue Type:
Improvement
Assignee:
Tomasz Szandała
Components:
configuration-as-code-groovy-plugin
Created:
2019-11-19 09:25
Environment:
Jenkins 2.176.4 OpenJDK Runtime Environment 11.0.5+10-LTS Linux 3.10.0-957.27.2.el7.x86_64 configuration-as-code-groovy-plugin 1.1 Running on OpenShift container platform.
Labels:
plugin jcasc configuration-as-code
Priority:
Minor
Reporter:
Cyril Marin
jCasC-Groovy plugin is not expanding variables from definitions because the feature is not implemented yet. Example:
// Variables not expanded, in the case of jCasC defined variables
groovy:
- url: https://${USER}:${PASS}@web.site.com/path/of/my/resource
groovy:
- script: println("${MY_VARIABLE}")
I made a Pull Request on Github project ==> https://github.com/jenkinsci/configuration-as-code-groovy-plugin/pull/3
