Declaritive scm step runs with minimal environment, makes it impossible to use environment value for reference repo path

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      I wanted to use the local reference clone option with an environment variable. Because the local reference directory is slightly different on every agent. I did this in the past with the Freestyle projects and it worked like a charm. I override the variable in every node.

      This doesn't work with pipeline multibranch projects. The clone option will not expand the variable because the build hasn't propagated them yet. Because the initial scm step is to clone the repo and pipeline and then run the pipeline and configure the build environment.

      Without environment variable support this feature is useless for me

            Assignee:
            Unassigned
            Reporter:
            Manfred Endres
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: