Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Pipe definition fetch error

Mike Burton June 13, 2019

So I've created my pipe repo and container, and now I'm trying to use the pipe using the repo reference syntax:

 

pipelines:
custom:
testenv1:
- step: *copyCodeToSharedStorage
- step:
script:
- pipe: myorg/run-tagged-tests:0.3.0
variables:
HOST: testenv1.domain.com
TAG: testTag1

When I run the above pipeline, I get the error "Pipe definition fetch error" during the build kickoff. The 0.3.0 tag does exist in both the repo and upstream in dockerhub. Not sure what else to look at.  

The *copyCodeToSharedStorage step just does a cp -r of all the code in the main pipeline repo (which also contains our test and production code) to the BITBUCKET_PIPE_SHARED_STORAGE location. I don't think it's causing this failure, though I'm admittedly not well-versed in all this.

1 answer

1 accepted

0 votes
Answer accepted
Tom Bradshaw
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 16, 2019

Hi Mike,

This normally occurs when there's a problem with the pipe.yml file. Unfortunately without more information we can't diagnose the specific issue.

Could you please add the pipe.yml file or create a support ticket at https://support.atlassian.com/ so we can look in to this further.

Cheers,
Tom.

Tom Bradshaw
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 17, 2019

New information: This can also be caused if the image name in the pipe.yml file is not well-formed and compliant with docker naming conventions. e.g.

image: and&two

 It would be a good idea to check this in your file.

Cheers,

Tom

Mike Burton June 18, 2019

It seems the problem was with $BITBUCKET_PIPE_SHARED_STORAGE_DIR not being defined at the top level.

We've had to back off of the pipe approach anyway, so I'll just close this question. I ended up just doing a parallel step-set inside a custom pipeline to do test subset reruns, which was the original purpose of the pipe.    

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events