Pipeline fails with "Error" when adding multiple steps

Pradeep Vanga

When I am adding additional steps to an existing pipeline, build just fials with status "Error" with no futher information as to why it is failing.

Build time is "0s" and opening the result leads to an infinite loader with a blank screen.

If I comment one of the steps, things work fine.

  branches:

    containerization:

      - step:

          name: Publish assets to s3 bucket

          deployment: test

          image: atlassian/pipelines-awscli

          script:

            - ./deploy-s3

      - step:

          name: Restart docker containers on remote server

          deployment: test

          script:

            - ./scripts/app-restart.sh

Pradeep Vanga

wow, this is really bad.. the issue is that I am setting the deployment: test to use the env specific variables in these steps.. turns out it is not supported

https://jira.atlassian.com/browse/BCLOUD-18261

 

UI wasn't showing any feedback, I had to go through the request, and responses in browser console to see the actual error. I spent hours trying various combinations to understand why things are failing sometimes even though everything looks correct.

 

I also had similar issues with docker build where some of the things were getting killed it seems, but there was no feedback in the docker build logs that an OOM event happened.. after shooting in the dark for long, increasing the memory helped.