Thanks Aravind,
I think it's enough to consider the issue is closed. I've solved it in the
similar way.
On Tuesday, October 1, 2019 at 2:44:58 PM UTC+3, Aravind SV wrote:
>
> However, as documented at
> https://docs.gocd.org/current/faq/dev_use_current_revision_in_build.html,
> it is possible
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
>
> 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
> 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
wrote:
> Hey, are you running on windows or linux agent?
>
>
>
> El domingo, 29 de septiembre de 2019, 6:10:27 (UTC-6), Maxim Shaev
&g
Hi guys, Is it possible to define a custom environment variable based on
standard?
e.g.
```
${GO_PIPELINE_LABEL}
```
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
>
>
> Did you try cancelling and rerunning the job?
>
>
OMG, thanks! It works! It took the latest changes after cancelling and
rerunning.
I had hoped recreating the pod should solve the issue, because didn't find
any other temporary files in the Persistence Volume. It looks like, the
server
