Do you have a node() {} around your stage?
On Fri, Dec 1, 2017 at 8:40 AM nk <[email protected]> wrote:
> I have a pipeline stage that does the following:
>
> * login to ECR (via groovy script in pipeline library)
> * docker build (via groovy script in pipeline library)
> * docker push to ECR (via groovy script in pipeline library)
>
> The problem I'm seeing is that any of these steps can run on a different
> executor (in the same slave) from the other steps. This results in a
> docker
> push failing on one executor because the login to ECR happened in another
> executor.
>
> 1. Is there a better pattern/practice I should be using?
> 2. Is there a way to force jenkins to use the same executor for all these
> steps?
>
> Thanks!
>
>
>
> --
> Sent from:
> http://jenkins-ci.361315.n4.nabble.com/Jenkins-users-f361316.html
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" 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/jenkinsci-users/1512072153155-0.post%40n4.nabble.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" 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/jenkinsci-users/CAPiUgVcVtktgVrqH1_W06hH4ey%3DRFonTBY8QFxiC_A9q942%3Djw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
