It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

atlassian/aws-sam-deploy Pipe in multiple steps giving permission error

I am using "atlassian/aws-sam-deploy" Pipe in multiple steps of pipeline. The pipe in the first step work with out any issue but the second pipe showing below error.

[Errno 13] Permission denied: '/opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/aws-sam-deploy/packaged.yml'

 

# This is a sample build configuration for Java (Gradle).
# Check our guides at https://confluence.atlassian.com/x/zd-5Mw for more examples.
# Only use spaces to indent your .yml configuration.
# -----
# You can specify a custom docker image from Docker Hub as your build environment.
image: openjdk:8
pipelines:
default:
- step: &build
name: Build
caches:
- gradle
artifacts: # defining the artifacts to be passed to each future step.
- build/**
script:
- bash ./gradlew build
branches:
develop:
- step: *build
- step:
name: DeployDev
deployment: develop
artifacts: # defining the artifacts to be passed to each future step.
- build/**
script: # Modify the commands below to build your repository.
- pipe: atlassian/aws-sam-deploy:0.1.3
variables:
AWS_ACCESS_KEY_ID: DEV_AWS_ACCESS_KEY
AWS_SECRET_ACCESS_KEY: DEV_AWS_SECRET_KEY
AWS_DEFAULT_REGION: DEV_AWS_DEFAULT_REGION
S3_BUCKET: DEV_S3_BUCKET
STACK_NAME: 'generic'
SAM_TEMPLATE: SAM_TEMPLATE
CAPABILITIES: ['CAPABILITY_IAM', 'CAPABILITY_AUTO_EXPAND']
WAIT: DEPLOYMENT_WAIT
WAIT_INTERVAL: WAIT_INTERVAL
- step:
name: DeployStage
deployment: stage
trigger: manual
script: # Modify the commands below to build your repository.
- pipe: atlassian/aws-sam-deploy:0.1.1
variables:
AWS_ACCESS_KEY_ID: DEV_AWS_ACCESS_KEY
AWS_SECRET_ACCESS_KEY: DEV_AWS_SECRET_KEY
AWS_DEFAULT_REGION: DEV_AWS_DEFAULT_REGION
S3_BUCKET: DEV_S3_BUCKET
STACK_NAME: 'generic'
SAM_TEMPLATE: SAM_TEMPLATE
CAPABILITIES: ['CAPABILITY_IAM', 'CAPABILITY_AUTO_EXPAND']
WAIT: DEPLOYMENT_WAIT
WAIT_INTERVAL: WAIT_INTERVAL

 

1 answer

Hi Mufeed did you end up figuring this out?

Yes.. removing state file solved the problem. Add below line at the end of the step

- rm /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/atlassian/aws-sam-deploy/packaged.yml

Like Jesse Colville likes this

Thanks this fixed my issue!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket Pipelines

What We Learned When We Researched Open Source Vulnerabilities in 7 Popular Coding Languages

...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...

1,042 views 0 3
Read article

Community Events

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

Events near you