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

Matrix jobs defaullt to "locked"

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hello,

      I would like to request feature change about locking matrix build with dependencies to other builds.

      Right now it's only possible to delete those builds via console on file system level directly.
      A real dependency would mean, if I delete those build for example #42, it should break the dependency to another build #43. This break would mean, it isn't possible to build #43. What doesn't happen in most cases.

      In this case it should be possible to allow "delete build" (at least as admin, because he/she knows what he/she does).

      Thanks & regards
      Gino

        Attachments

          Activity

          giat7133 Gino Atlas created issue -
          giat7133 Gino Atlas made changes -
          Field Original Value New Value
          Environment Jenkins version 2.30
          Matrix project plugun version 1.7
          Jenkins version 2.30
          Matrix project plugin version 1.7
          Hide
          jladan James Ladan added a comment -

          For us, this isn't an improvement request – the current behaviour is a bug, and a moderately significant one at that.

          We have one project with far too many configuration possibilities, and the matrix config build job ends up with a chain of locked builds that cannot be removed, with the note "build X depends on this". The builds are independent, started from different branches of the source and using different configuration combinations.

          Periodically, I have to manually remove all builds, in order to clear out old builds going back weeks, because a dependency chain has formed from the oldest right through to the newest.

          Show
          jladan James Ladan added a comment - For us, this isn't an improvement request – the current behaviour is a bug, and a moderately significant one at that. We have one project with far too many configuration possibilities, and the matrix config build job ends up with a chain of locked builds that cannot be removed, with the note "build X depends on this". The builds are independent, started from different branches of the source and using different configuration combinations. Periodically, I have to manually remove all builds, in order to clear out old builds going back weeks, because a dependency chain has formed from the oldest right through to the newest.

            People

            Assignee:
            kohsuke Kohsuke Kawaguchi
            Reporter:
            giat7133 Gino Atlas
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated: