Bitbucket cloud trigger pipe

Question

Is it possible for a triggered pipeline to pass information back to the repository pipeline which triggered it?

For example, if repo my-lib triggers a rebuild of my-app, is there a way to pass information back to the pipeline in my-lib for further action other than simple success or failure?

Mark C · Answer

Hi @plussier

Indeed, the trigger Pipes script is run from a REST API to trigger Pipelines returning the exit status of the Pipelines build ran.

When you mentioned B passing back data to A, without disclosing any sensitive information, could you let me know what type of data you'd like to pass back to A? Is it some kind of status values or set of artifacts?

Regards,
Mark C

plussier_hplmja · Answer

Hi Marc,

Passing data back from the triggered pipeline using variables is exactly what I'd like to do, that was basically my initial question. I'm just not clear on how that works. I don't see anything in docs for the trigger pipe that says there's any exit data passed back to the triggering pipeline. As far as I can tell, the trigger pipe simply makes a BB API call to run a remote pipeline, then polls for it's exit status (success or failure).

Containerizing the library isn't useful in this case.   The goal is to be able to use information passed back in subsequent steps in the triggering pipeline.  In other words:

* A triggers B
* B does whatever, and exits passing back data to A
* A then moves on, using the data passed back in follow-on steps.

Containerizing the repository from A doesn't help me as far I can tell.

--

Paul

Mark C · Answer

Hi Paul,

True, it may be messy to manage especially when builds becomes busy. Indeed, you can try passing through data using variables or through the use of Caches.

Alternatively, you can try to containerize the library using Bitbucket Cloud Packages and update it from your desired build step.

Regards,
Mark C