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 you, Varsha On Sat, Sep 7, 2019, 12:00 Maxim Shaev <[email protected]> wrote: > >> 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 keeps the current stage/session in DB. > > Thank you again. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/go-cd/05ac76be-8b27-4ef0-8810-04ddc9aa3152%40googlegroups.com > <https://groups.google.com/d/msgid/go-cd/05ac76be-8b27-4ef0-8810-04ddc9aa3152%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAEno-p7M64yAxfm7R98urz-ZKjc%3D6fdKWuH5uQ%3DqQ_%2Bii0Z%2BEg%40mail.gmail.com.
