We want to use Jenkins Jobs to trigger our Functional Acceptance Tests (FAT), which run on a remote position.
As these tests can typically take quite some time (up to a few hours) we cannot block an executor thread for the whole time.

Therefore it would be great if there is an option to manually trigger builds in a pipeline from outside via REST API. i.e.

Job A (Builds the App & deploys it - Triggered by SCM)
Job B (Starts a remote FAT test - Triggered by successfull JOB A)
Job C (If the tests are successful Job C is triggered via REST callback)

Currently there is no obvious possibility to illustrate/run Job C as part of a Build Pipeline instance.

Possible solution: Introduce a "Build Pipeline ID" parameter, which could i.e. be passed with REST that assigns a triggered job to a Build Pipeline instance.