You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
- ./gradlew build
name: Push To Deployer
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.