You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.