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

Option to mark a phase/job as non-blocking/asynchron

XMLWordPrintable

      Have a option like the "disable job" option to mark a phase/job as
      e.g.

      • non-blocking
      • asynchron
      • non-waiting

      This phase/job is executed in normal manner of the pipeline but does not block the execution cycle of the surrounding multijob.

      For example:
      A multijob M with three phases:

      Phase 1: A
      Phase 2: B
      Phase 3: C + D

      M has several post-builds (with conditions). B,C,D are multijobs itself.
      C is a multijob containing jobs (e.g. maintenance jobs), which can take very long. This job can be executed asynchron, so that the surrounding multijob M can finish an execute it's post builds and a result can be generated.
      The result of C is not important for the result of M, but should be shown within the pipeline of M.

          [JENKINS-26876] Option to mark a phase/job as non-blocking/asynchron

          lx last created issue -
          lx last made changes -
          Summary Original: Option to mark a phase as non-blocking / asynchron phase New: Option to mark a phase/job as non-blocking/asynchron

          Mathieu Cantin added a comment -

          I invit you to see this pull request, https://github.com/jenkinsci/tikal-multijob-plugin/pull/59

          Mathieu Cantin added a comment - I invit you to see this pull request, https://github.com/jenkinsci/tikal-multijob-plugin/pull/59

          lx last added a comment -

          @ Mathieu Cantin added a comment - 18/Mar/15 2:46 PM
          I invit you to see this pull request, https://github.com/jenkinsci/tikal-multijob-plugin/pull/59

          Hi and thanks for this info. Unfortunately i don't see the solution in that.
          I do not want the throttle a job respectively to another job in the same phase, i want a surrounding multi-job to be able to finish although a job in the pipeline is still running.
          Important is, that this job should be shown in the pipeline. If not, it could just be realized with a "trigger build on other project".

          regards

          lx last added a comment - @ Mathieu Cantin added a comment - 18/Mar/15 2:46 PM I invit you to see this pull request, https://github.com/jenkinsci/tikal-multijob-plugin/pull/59 Hi and thanks for this info. Unfortunately i don't see the solution in that. I do not want the throttle a job respectively to another job in the same phase, i want a surrounding multi-job to be able to finish although a job in the pipeline is still running. Important is, that this job should be shown in the pipeline. If not, it could just be realized with a "trigger build on other project". regards
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 161052 ] New: JNJira + In-Review [ 180555 ]

          Yoram Michaeli added a comment -

          Closing issue as part of tikal-multijob-plugin issues cleanup.
          If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)

          Yoram Michaeli added a comment - Closing issue as part of tikal-multijob-plugin issues cleanup. If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)
          Yoram Michaeli made changes -
          Resolution New: Postponed [ 6 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            lxndr lx last
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: