You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
name: build (alt)
- echo "Building..."
- npm install -f && npm install -g @angular/cli && mkdir -p out/
- npm run build:alt && tar --owner=0 --group=0 --numeric-owner -czvf out/doctor-alt.tar.gz -C dist/ .
- npm run build:training && tar --owner=0 --group=0 --numeric-owner -czvf out/doctor-training.tar.gz -C dist/ .
- echo "Uploading artifacts to S3..."
- pipe: atlassian/aws-s3-deploy:0.3.2
This pipeline was running for a longtime without any issue. Suddenly this came up without changing anything to the bitbucket-pipelines.yml file or env variables
Hello @Achala Dissanayake and welcome to the Community!
The error returned in the logs is usually related to the file in question (out/doctor-alt.tar.gz) not existing at the location or path the build process is expecting it to be in. I see you have opened an internal ticket with us related to this issue and one of our support engineers is already working on that ticket. Once the ticket is resolved, feel free to share the solution here, so other users that might face the same issue in the future can try similar steps.
Thank you, @Achala Dissanayake !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.