Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Rerunning custom pipeline does not include the input variables

Jesus Pena Mateos
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 9, 2025

Hello, 

I have create a custom pipeline to run it manually with some input parameters. The first run works just fine. The problem comes when I try to re-run it. It allows me to re-run the pipeline but it does not use the previous input parameters established and it complains of those not being set. 

Is there anything ongoing to resolve this issue or could I fix it somehow?

Thank you!

I leave the definition of the pipeline in case it helps:


custom:

manual-deployment:

- variables:

- name: ACCOUNT_ID

default: ""

- name: ACCOUNT_NAME

default: ""

- name: STACK

default: "platform"

- name: ACCOUNT_TYPE

default: "partner"

- name: CONFIG_TYPE

default: "infrastructure"

- name: PLATFORM_LIBRARY_VERSION

default: ""

- step:

<<: *common

name: Manual Deployment

script:

- *platform_root_login

- *jfrog_pypi_login

- if [ -z "$ACCOUNT_ID" ] || [ -z "$ACCOUNT_NAME" ]; then echo "ACCOUNT_ID and ACCOUNT_NAME variables must be set"; exit 1; fi

1 answer

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 11, 2025

Hi Jesus,

This is a known bug with Pipelines and is being tracked with our development team in the ticket below - please feel free to Watch this to receive future updates related to it:

You'll need to run the custom build again directly from the pipelines page, rather than clicking re-run on the build screen.

Cheers!

- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events