When running the aw-lambda-deploy pipe I am seeing the following error, the lambda is being updated.
INFO: Update command succeeded.
INFO: Writing results to file /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/aws-lambda-deploy-env.
//update-lambda.sh: line 22: /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/aws-lambda-deploy-env: Permission denied
I thought it may be memory related so increased the size of the step but continue to see the issue, this worked previously when I had less steps.
The failing pipeline.yml file is:
caches: # Marks what will be in cache so it is not downloaded again.
script: # Modify the commands below to build your repository.
- pip install -r requirements.txt
- pip install -r requirements-dev.txt
- make coverage
- ls -list
name: Sonar Scan
- pipe: sonarsource/sonarcloud-scan:1.0.1
EXTRA_ARGS: '-Dsonar.test.inclusions="**/*_test.py" -Dsonar.verbose=true'
- pipe: sonarsource/sonarcloud-quality-gate:0.1.3
name: Build Lambda
# Build Lambda
- make archive
# Update lambda code and publish a new version
- pipe: atlassian/aws-lambda-deploy:0.5.3
If I run the Build Lambda step alone then it works.
I tried the workaround on this question but the file dos not exist so cannot be removed.
Any tips appreciated.
@John C I have some questions to define the root cause:
* did it work previously with the same version?
* what exactly steps did you add since the time it worked? Could the be the reason of failure? Are you doing something specific with BITBUCKET_PIPE_SHARED_STORAGE_DIR directory in those added steps?
* You can add to your pipeline each step one by one (except of lambda deploy pipeline) to define, what exactly is failing permissions to that directory
Looking fowrard to hearing from you again.
I manged to narrow this down to the sonarcloud pipes. If I remove the sonar step then the pipelines work, if I run the sonar step alone as a manual pipeline then that works. I haven;t spent much time looking further into this as this repo is not particularly active and does not require the sonar scan of every action so we simply separated it out.
If you delete the shared location directory before running the lambda deploy pipeline then everything works as expected.
Still would be good to know why the sonarcloud pipes prevent other pipes from writing to that shared location
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
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