Substitutions in environment variable

[Maxim Shaev]

Hi guys, Is it possible to define a custom environment variable based on standard?

e.g.

```

        <environmentvariables>

          <variable name="APP_VERSION">

            <value>${GO_PIPELINE_LABEL}</value>

          </variable>

```

That doesn't work as expected. The results:

```

GO_PIPELINE_LABEL=dev-107

APP_VERSION=${GO_PIPELINE_LABEL}

```

If no, what's the best way to define that variable?

[Manuel Ortiz]

Hey, are you running on windows or linux agent?

[Maxim Shaev]

> Hey, are you running on windows or linux agent?

Hey, It's Linux (Ubuntu 18.04 server) agent

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/464f6d6b-8f40-4c34-9e8c-dffc7129cc75%40googlegroups.com.

--

Best regards,
Maxim Shaev

[Jason Smyth]

Hi Maxim,

Maybe I am missing something but why do you want to do this?

Could you not reference the existing variable instead of creating a custom variable that contains the same data?

Regards,

Jason

On Monday, 30 September 2019 02:44:46 UTC-4, Maxim Shaev wrote:

> Hey, are you running on windows or linux agent?

Hey, It's Linux (Ubuntu 18.04 server) agent

On Mon, Sep 30, 2019 at 5:02 AM Manuel Ortiz <jmanue...@gmail.com> wrote:

Hey, are you running on windows or linux agent?

El domingo, 29 de septiembre de 2019, 6:10:27 (UTC-6), Maxim Shaev escribió:

Hi guys, Is it possible to define a custom environment variable based on standard?

e.g.

```

        <environmentvariables>

          <variable name="APP_VERSION">

            <value>${GO_PIPELINE_LABEL}</value>

          </variable>

```

That doesn't work as expected. The results:

```

GO_PIPELINE_LABEL=dev-107

APP_VERSION=${GO_PIPELINE_LABEL}

```

If no, what's the best way to define that variable?

--
You received this message because you are subscribed to the Google Groups "go-cd" group.

To unsubscribe from this group and stop receiving emails from it, send an email to go...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/464f6d6b-8f40-4c34-9e8c-dffc7129cc75%40googlegroups.com.

[Maxim Shaev]

Hi, Jason

 

Could you not reference the existing variable instead of creating a custom variable that contains the same data?

Unfortunately no, these variables are expected to get as environment variables for k8s manifest template to prepare the manifest file.

Currently the issue is solved by Linux way to set env. variables before command

e.g.

gocd_image_path=${IMAGE_PREFIX}/${GO_PIPELINE_NAME}:${GO_PIPELINE_LABEL} dump-env --template=.env.dist --prefix='gocd_' > .env

[Aravind SV]

Hello Maxim,

Yes, GoCD doesn't substitute environment variables like $GO_PIPELINE_NAME etc. when defining other environment variables.

However, as documented at https://docs.gocd.org/current/faq/dev_use_current_revision_in_build.html, it is possible to get bash to do that for you. It also gives you much more flexibility, since it allows you to do things like: ${ENV_VAR:-default}.

In your case, as long as the command is "sh" or "bash" and the first argument is "-c", you should be able to use exactly what you showed there.

Cheers,
Aravind

[Maxim Shaev]

Thanks Aravind,

I think it's enough to consider the issue is closed. I've solved it in the similar way.