Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,455,816
Community Members
 
Community Events
176
Community Groups

can't open '$BITBUCKET_PIPE_SHARED_STORAGE_DIR/aws-lamda-deploy-env': No Such file or directory

rizwanaparveen.abdulla
rizwanaparveen.abdulla Mar 10, 2020

Running pipe aws-lambda-deploy  shows writing result to the $BITBUCKET_PIPE_SHARED_STORAGE_DIR/aws-lamda-deploy-env but when I try to Open it shows no file/ Directory

Answer
Watch
Like Be the first to like this
274 views

2 answers

1 accepted

0 votes
Answer accepted
John C
John C Jun 10, 2020

I worked around this by using:

 

- VERSION=$(jq  --raw-output '.Version' /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/aws-lambda-deploy-env)

 

Not ideal but it's allowed my pipeline to work 

Reply
0 votes
Malte Hübner
Malte Hübner Dec 15, 2021 • edited

Must be a bug because here you can find an example of a correct usage: https://bitbucket.org/blog/updates-to-bitbucket-pipes.

For example: To access the aws-lambda-deploy-env file from the aws-lambda-deploy pipe you would write:

cat $BITBUCKET_PIPE_SHARED_STORAGE_DIR/atlassian/aws-lambda-deploy/aws-lamda-deploy-env


It's just what @rizwanaparveen.abdulla tried to achieve.

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS

Atlassian Community Events

See all events