Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,103
Community Members
 
Community Events
176
Community Groups

Pipeline fails with "Error" when adding multiple steps

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

error.jpgloader.jpg

1 answer

1 accepted

1 vote
Answer accepted

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.

Patrik S Atlassian Team Jan 12, 2023

Hey @Pradeep Vanga ,

Welcome to Atlassian Community!

Reading through your last comment, my understanding is that you would like to use your deployment variables in more than one step, i.e., a multi-step deployment.

By the time I write this message, we have a Beta feature available called Stages, which allows you to group pipeline steps and configure shared properties, such as grouping deployment steps.

Please allow me to share an example of how to configure your YAML file to use a multi-step deployment : 

pipelines:
   default:
    - stage:
        name: Build and test
        deployment: staging
        steps:
          - step:
              name: Build app
              script:
                - sh ./build-app.sh
          - step:
              name: Run unit tests
              script:
                - sh ./run-tests.sh

In this example, any deployment variable setup for the environment staging would be available for both of the steps.

For more details and examples of using stages, you're also welcome to check our Stages official documentation.

Thank you, @Pradeep Vanga !

Patrik S

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events