Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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 # people like this

Thanks this fixed my issue!

Thank you, was driving me nuts!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

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

190 views 2 1
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