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

Block the job from starting in case no critical block start is present in the build steps

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • exclusion-plugin
    • None

      In order to make use of this plugin in my CI I need to be able to block the build before it consumes a slave nodes executor. The reason for that is that I have a large number of Matrix combinations that compete for exclusive access to shared resources, spread across multiple Matrix jobs.

      Example:
      Matrix A: Browser X Server (Jobs runs on Browser)
      Matrix B: Server X Agent (Job runs on Agent, needs to lock agent)
      Matrix C: Browser X Server X Agent (Job needs to lock Agent and run on Browser)
      Matrix A and B can run in parallel without coordination in my case, Matrix C however needs to coordinate resources with both A and B.

      Currently Matrix A and B exist and manage resource access with only a single executor per slave, this won't work for Matrix C however.

      While my requirement could be fulfilled already by adding lots of executors to every slave that would make my Jenkins installation quite unclear

          [JENKINS-29319] Block the job from starting in case no critical block start is present in the build steps

          There are no comments yet on this issue.

            Unassigned Unassigned
            cobexer Ing. Christoph Obexer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: