Hello,
Yes, the elastic profile is stored in the DB for the job and deleted later
on after job completion. So, if you wanted an already scheduled job to use
another elastic profile, you need to rerun.
Maybe there is some improvement that can be done in case of invalid pod
yaml. Not sure.
Thank
>
>
> 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
Hello,
Did you try cancelling and rerunning the job?
Thanks,
Varsha
On Saturday, 7 September 2019 10:03:05 UTC-7, Maxim Shaev wrote:
>
> Hi guys,
>
> I've successfully install GoCD through helm. The sample pipeline is
> successfully built using Kubernetes Elastic Agent.
> While I was adding a
