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.
It looks like you're new here. Sign in or register to get started.
