Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33837

Option to wait for transitive downstream builds to complete

    XMLWordPrintable

Details

    Description

      Given a pipeline script, I configure to execute a build step to build a (existing) job:

      build job: 'Project-Build-Job1_Kickoff', wait: true

      The job is triggered successfully, and the pipeline waits for its completion. But, the called build job has a post-build action defined of kind "trigger parameterized build on other project". The pipeline does not wait for the downstream build, only for the first one in the chain which is referenced by name in the pipeline script. It is expected that the existing functionality is used and embedded "as is", thus pipeline waits for completion of complete downstream chain.

      Update: this works as a sequence of build jobs linked with Post Build Actions. Triggering the first one via Pipeline, the downstreamed ones are triggered as well, but the Pipeline does not block until completion. This is critical because this prevents migration.

      Attachments

        Issue Links

          Activity

            jglick Jesse Glick added a comment -

            As designed—you should either make the immediate downstream project use a blocking trigger, or remove the triggers from the freestyle projects entirely and use Pipeline to orchestrate the whole thing—though it would be useful to have such an option for integration with existing freestyle project chains.

            jglick Jesse Glick added a comment - As designed—you should either make the immediate downstream project use a blocking trigger, or remove the triggers from the freestyle projects entirely and use Pipeline to orchestrate the whole thing—though it would be useful to have such an option for integration with existing freestyle project chains.

            Hi jglick, yes, exactly, as described, the use case is to have an option for integration with existing project chains.
            It could be particular intersting for users to have this option as part of a migration path, which is often helpful with new versions of tools.

            michaelhuettermann Michael Hüttermann added a comment - Hi jglick , yes, exactly, as described, the use case is to have an option for integration with existing project chains. It could be particular intersting for users to have this option as part of a migration path, which is often helpful with new versions of tools.
            abayer Andrew Bayer added a comment -

            If the downstream build doesn't itself wait for its own downstreams to complete, I don't think it makes sense to add additional logic to the build step to watch for downstreams of the downstreams and so forth and wait for them too.

            abayer Andrew Bayer added a comment - If the downstream build doesn't itself wait for its own downstreams to complete, I don't think it makes sense to add additional logic to the build step to watch for downstreams of the downstreams and so forth and wait for them too.

            People

              Unassigned Unassigned
              michaelhuettermann Michael Hüttermann
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: