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

Provide a 'prerequisites' sections (like triggers) that allows blocking the execution of a job

    XMLWordPrintable

Details

    Description

      This is a proposal to fulfill requirements like in JENKINS-37718 in a more general way.

      The proposal is to add a new prerequisites section, where we can define conditions that should prevent a job from beeing run even if there was a trigger, similar to what alreaddy happens if there is no free build-executor, so the job simply waits untill the prerequisites are meet.

      prerequisites might include

      1. wait until other jobs are build
      2. trottle builds
      3. do not build when another job has a failed status

      Attachments

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-37718 Block Pipeline job while upstream or downstream projects are building

          • Major - Major loss of function.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-42643 Conditional application of triggers in Declarative

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-67402 Conditional post action depending on which trigger

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            laeubi Christoph Läubrich added a comment -

            As a background: We have an automated UI test that is triggered by the upstream build. Of course it can also happen that the testcode itself is adjusted so we also have an SCM trigger.

            If the previous job fails or is currently building we want to block the ui test regardless of SCM change or a user is triggering such a build.

            laeubi Christoph Läubrich added a comment - As a background: We have an automated UI test that is triggered by the upstream build. Of course it can also happen that the testcode itself is adjusted so we also have an SCM trigger. If the previous job fails or is currently building we want to block the ui test regardless of SCM change or a user is triggering such a build.

            People

              Unassigned Unassigned
              laeubi Christoph Läubrich
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: