Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,300,178
Community Members
 
Community Events
165
Community Groups

trigger-pipeline pipe never completes if pipeline has a manual deployment step

I have been successfully using the atlassian/trigger-pipeline:4.0.2 pipe to trigger and run multiple pipelines, waiting for success or failure.  I have a "master build" that runs a list of pipelines in several other repos.  My steps invoking the trigger specify WAIT: 'true'

The default pipelines are being triggered and typically take 1-3 minutes to run to completion.   This has all been working fine.

I recently added a manual deployment step to some of the pipelines.  Now the trigger-pipeline steps for the repos where I've added the manual deployment step to those pipelines never get's back a successful completion.  The following lines repeat forever, even though I can verify the triggered pipeline has successfully completed:

INFO: Attempt number 22: Getting build info.
INFO: Attempt number 22: Build number 10 for MyBuild is IN_PROGRESS, waiting for pipeline to finish...

The pipelines without the added deployment steps continue to work, but those with the manual deployment steps do not.  Does this pipe support waiting for pipelines with manual deployment steps?  For example, triggering the pipeline with this step never comes back as successful:

pipelines:
default:
- step:
caches:
- gradle
script:
- ./gradlew build
artifacts:
- dist/*.jar
- step:
name: Push To Deployer
deployment: Test
trigger: manual
script:
- /pushToDeployer.sh

I am only expecting that the ./gradlew build step needs to complete successfully, and the pipeline shows a status of Successful in the UI. However the trigger-pipeline pipe waits forever.  I tried updating to use atlassian/trigger-pipeline:4.0.3 but that didn't help.

0 comments

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,257 views 2 9
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you