Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60209

jCasC-Groovy not expanding variables

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • configuration-as-code-groovy-plugin
    • 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.

      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

       

       

          [JENKINS-60209] jCasC-Groovy not expanding variables

          Maciej Wolniewicz added a comment -

          szandala 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.

          Maciej Wolniewicz added a comment - szandala 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.

            szandala Tomasz Szandała
            ziouf Cyril Marin
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: