alt:
- step:
name: build (alt)
caches:
- node
script:
- 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/ .
artifacts:
- out/*
- step:
name: upload
script:
- echo "Uploading artifacts to S3..."
- pipe: atlassian/aws-s3-deploy:0.3.2
variables:
AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY
AWS_DEFAULT_REGION: 'eu-west-2'
S3_BUCKET: 'build-artifacts'
LOCAL_PATH: 'out'
Error
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 !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.