• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • build-pipeline-plugin
    • None
    • Jenkins 1.5.37
      Build Pipeline Pugin 1.4.1

      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.

          [JENKINS-20321] Chaining Jobs via REST Callback

          Rick added a comment -

          You can use pipeline step – build, this step can trigger another job.

          Rick added a comment - You can use pipeline step – build, this step can trigger another job.

          You can trigger builds and wait for them to complete using the REST API. See an example in the cdancy/jenkins-rest wiki.

          Martin d'Anjou added a comment - You can trigger builds and wait for them to complete using the REST API. See an example in the  cdancy/jenkins-rest wiki .

            Unassigned Unassigned
            sleonhar Stefan Leonhartsberger
            Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: