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

How to make custom pipe works

Adrian Lapierre September 1, 2024

I have simple custom pipe: 

https://bitbucket.org/itrust-dev/call-webhook-pipe/

 

Image is build and pushed to DockerHub and it is public available (`docker pull lapierre/call-webhook:1.0.0` works) .

 

My pipeline looks like this:

 

- step:
name: Deploy Dev
trigger: 'manual'
deployment: Test
clone:
enabled: false
script:
- VERSION=$(cat version.env)
- echo $VERSION
- FULL_URL="${WEB_HOOK_URL}?SERVICE_VERSION=${VERSION}"
- pipe: lapierre/call-webhook:1.0.0
variables:
ITRUST_WEBHOOK_URL: ${FULL_URL}

 

I got error from BitBucket: Configuration error It looks like you tried to use a pipe in your bitbucket-pipelines.yml that doesn’t exist. Check the name of the pipe and try again.

What I'm doing wrong?

1 answer

1 accepted

2 votes
Answer accepted
Adrian Lapierre September 3, 2024

There are 2 ways to refer to this pipe in other repositories. In your bitbucket-pipelines.yml file you can:

  1. refer to the docker image directly 
    pipe: `docker://acct/repo:tag` (where acct/repo is the Dockerhub account and repo) Note: You must always specify `docker://` when referencing public Docker images.
  2. refer to a pipe repo hosted on Bitbucket
    pipe: `<BB_acct>/repo:tag` (where BB_acct/repo is your Bitbucket account and pipe repo)
    This version of the reference looks in your pipe.yml file to find out where to get the image from.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events