I use atlassian/aws-lambda-deploy as pipe to deploy code to AWS Lambda, I have 2 environments , and they are dev and production. However, after deploying to dev successfully, and going to production deployment, it fails at step update-lambda.sh whereas I believe the code deployed successfully to production, it just marks the status failed due to lacking permission to write artifacts files
There is a work around solution that we need to run this command at the end of each lambda deployment step (except the last one) to clean the artifacts data
rm -rf /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/aws-lambda-deploy-env
Hopefully, the team will fix this problem soon by upgrading the image.
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events