Skip to content

[JENKINS-10197] Matrix jobs default to "locked" (and are difficult to delete) #15938

Closed
Bug
Closed
[JENKINS-10197] Matrix jobs default to "locked" (and are difficult to delete)#15938
Bug
Labels
component:corecomponent:matrix-project-pluginimported-jira-issuepriority:criticalresolution:fixed

Description

@jenkins-infra-bot
jenkins-infra-bot
opened on Jul 1, 2011

With a matrix job now when it completes it defaults to being a "keep forever" type build. Only by deleting the current job can a previous job be deleted, in some cases.

(09:36:12 AM) Tartarus: kohsuke: With matrix jobs and 1.418 I'm seeing all of my jobs default to being locked, didn't see this with 1.409, any ideas?
(09:36:32 AM) kohsuke: probably related to the partial rebuild support. Any ticket for this?
(09:36:54 AM) Tartarus: Hadn't filed one yet
(09:37:18 AM) kohsuke: Would you please? I don't think I can get it right now, but I don't want to forget
Originally reported by tomrini, imported from: Matrix jobs default to "locked" (and are difficult to delete)
  • assignee: vjuranek
  • status: Resolved
  • priority: Critical
  • component(s): core, matrix-project-plugin
  • label(s): 1.509.1-fixed
  • resolution: Fixed
  • resolved: 2016-11-08T11:27:25+00:00
  • votes: 24
  • watchers: 36
  • imported: 2025-11-24
Raw content of original issue 
With a matrix job now when it completes it defaults to being a "keep forever" type build.  Only by deleting the current job can a previous job be deleted, in some cases.




(09:36:12 AM) Tartarus: kohsuke: With matrix jobs and 1.418 I'm seeing all of my jobs default to being locked, didn't see this with 1.409, any ideas?
(09:36:32 AM) kohsuke: probably related to the partial rebuild support. Any ticket for this?
(09:36:54 AM) Tartarus: Hadn't filed one yet
(09:37:18 AM) kohsuke: Would you please? I don't think I can get it right now, but I don't want to forget
  • environment: 1.418, 1.434, 1.466
2 attachments

Activity

  1. jenkins-infra-bot commented on Jul 5, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 5, 2011
    Author
    tomrini:
    • Original comment link
    • Raw content of original comment: 
      Just now when I had one build spinning up and I tried to delete the previous one it says that can't delete build #182 because #183 depends on it (roughly, forgot to copy in time).

    Just now when I had one build spinning up and I tried to delete the previous one it says that can't delete build #182 because #183 depends on it (roughly, forgot to copy in time).

  2. jenkins-infra-bot commented on Jul 11, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 11, 2011
    Author
    abayer:
    • Original comment link
    • Raw content of original comment: 
      I ran into this a while back - the problem is that you've changed your axes, and now there's a chain of builds depending on each other back to the last one with the old axes. I got around this by deleting the actual directory from $JENKINS_HOME/jobs/$JOB_NAME/configurations/axis-label. That said, this is definitely still a real bug.

    I ran into this a while back - the problem is that you've changed your axes, and now there's a chain of builds depending on each other back to the last one with the old axes. I got around this by deleting the actual directory from $JENKINS_HOME/jobs/$JOB_NAME/configurations/axis-label. That said, this is definitely still a real bug.

  3. jenkins-infra-bot commented on Jul 13, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 13, 2011
    Author
    g01:
    • Original comment link
    • Raw content of original comment: 
      We have this issue as well. Because every build is kept and the logs are rather large, in approximately 2 months time, our logs are over 5GB for one job.

    We have this issue as well. Because every build is kept and the logs are rather large, in approximately 2 months time, our logs are over 5GB for one job.

  4. jenkins-infra-bot commented on Jul 26, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 26, 2011
    Author
    barrywark:
    • Original comment link
    • Raw content of original comment: 
      Also experiencing the same issue, and we're quickly filling up disk space on our master. Since we've saved release builds in the artifacts of jobs, I can't just delete the entire jobs/$JOB_NAME/configurations/axis-label folder (though I'll start working through and copying the artifacts out so that we can). Has anyone figured out how to delete particular builds when they're in this "locked" state?

    Also experiencing the same issue, and we're quickly filling up disk space on our master. Since we've saved release builds in the artifacts of jobs, I can't just delete the entire jobs/$JOB_NAME/configurations/axis-label folder (though I'll start working through and copying the artifacts out so that we can). Has anyone figured out how to delete particular builds when they're in this "locked" state?

  5. jenkins-infra-bot commented on Jul 27, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 27, 2011
    Author
    docwhat:
    • Original comment link
    • Raw content of original comment: 
      I have this problem too....
      


      I'm wondering if it's related to JENKINS-10131 - Git Plugin kicks off builds for executors.
      


      All the builds that are having this issue are triggered by git looking for workspaces.  I don't know if that's the case with the other builds.

    I have this problem too....

    I'm wondering if it's related to JENKINS-10131 - Git Plugin kicks off builds for executors.

    All the builds that are having this issue are triggered by git looking for workspaces. I don't know if that's the case with the other builds.

  6. jenkins-infra-bot commented on Jul 27, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 27, 2011
    Author
    barrywark:
    • Original comment link
    • Raw content of original comment: 
      Although we have the git plugin installed, all of the relevant builds are from SVN.

    Although we have the git plugin installed, all of the relevant builds are from SVN.

  7. jenkins-infra-bot commented on Jul 27, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 27, 2011
    Author
    tomrini:
    • Original comment link
    • Raw content of original comment: 
      I've ran a git bisect on this problem and it's:
      


      51c85a9fa030013553299e59649251b4f09560d5 is the first bad commit
commit 51c85a9fa030013553299e59649251b4f09560d5
Author: Kohsuke Kawaguchi <kk@kohsuke.org>
Date:   Thu May 12 10:50:18 2011 -0700
      


          control GC so that records are always full

    I've ran a git bisect on this problem and it's:

    51c85a9 is the first bad commit
    commit 51c85a9
    Author: Kohsuke Kawaguchi
    Date: Thu May 12 10:50:18 2011 -0700

    control GC so that records are always full

  8. jenkins-infra-bot commented on Jul 28, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 28, 2011
    Author
    docwhat:
    • Original comment link
    • Raw content of original comment: 
      Yeah, that isPartial() function looks wrong....

    Yeah, that isPartial() function looks wrong....

  9. jenkins-infra-bot commented on Jul 28, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 28, 2011
    Author
    docwhat:

    Link to the code in question: 51c85a9

  10. jenkins-infra-bot commented on Jul 29, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 29, 2011
    Author
    scm_issue_link:

    Code changed in jenkins
    User: Andrew Bayer
    Path:
    changelog.html
    core/src/main/java/hudson/matrix/MatrixBuild.java
    http://jenkins-ci.org/commit/jenkins/eea67c761e78fa1b26f9d2ae82826e3e74b877ee
    Log:
    [FIXED JENKINS-10197] isPartial() check for matrix builds now only reference active configurations.

  11. jenkins-infra-bot commented on Jul 29, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 29, 2011
    Author
    abayer:
    • Original comment link
    • Raw content of original comment: 
      Fix will be in 1.425.

    Fix will be in 1.425.

  12. jenkins-infra-bot commented on Jul 29, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Jul 29, 2011
    Author
    dogfood:

    Integrated in jenkins_main_trunk #1002
    [FIXED JENKINS-10197] isPartial() check for matrix builds now only reference active configurations.

    Andrew Bayer : eea67c761e78fa1b26f9d2ae82826e3e74b877ee
    Files :

    • changelog.html
    • core/src/main/java/hudson/matrix/MatrixBuild.java

  13. jenkins-infra-bot commented on Sep 12, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Sep 12, 2011
    Author
    scm_issue_link:

    Code changed in jenkins
    User: Andrew Bayer
    Path:
    changelog.html
    core/src/main/java/hudson/matrix/MatrixBuild.java
    http://jenkins-ci.org/commit/jenkins/eea67c761e78fa1b26f9d2ae82826e3e74b877ee
    Log:
    [FIXED JENKINS-10197] isPartial() check for matrix builds now only reference active configurations.

  14. jenkins-infra-bot commented on Sep 19, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Sep 19, 2011
    Author
    ebann:
    • Original comment link
    • Raw content of original comment: 
      I'm seeing this problem in Jenkins 1.430.
      


      Isn't it "resolved" ?

    I'm seeing this problem in Jenkins 1.430.

    Isn't it "resolved" ?

  15. jenkins-infra-bot commented on Oct 19, 2011

    @jenkins-infra-bot
    jenkins-infra-bot
    on Oct 19, 2011
    Author
    trbaker:
    • Original comment link
    • Raw content of original comment: 
      Please re-open.  I am seeing this behavior in 1.434

    Please re-open. I am seeing this behavior in 1.434

  16. 34 remaining items

  17. jenkins-infra-bot commented on Nov 8, 2016

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 8, 2016
    Author
    danielbeck:
    • Original comment link
    • Raw content of original comment: 
      giat7133 Please see the preceding comment. Thank you.

    giat7133 Please see the preceding comment. Thank you.

  18. jenkins-infra-bot
    closed this as completedon Nov 8, 2016

  19. jenkins-infra-bot commented on Nov 8, 2016

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 8, 2016
    Author
    giat7133:
    • Original comment link
    • Raw content of original comment: 
      So I will need to create an improvement request. Thank you!

    So I will need to create an improvement request. Thank you!

  20. jenkins-infra-bot commented on Aug 30, 2017

    @jenkins-infra-bot
    jenkins-infra-bot
    on Aug 30, 2017
    Author
    lukasova_m:
    • Original comment link
    • Raw content of original comment: 
      HI, I also have a multi-configuration job and i cannot delete any job, because it shows it depends on itself or another job. But that another job also depends on some. And it doesn't give me an option to unmark the build to be kept forever. Is there some solution? (Jenkins v. 2.27)
      


      Thanks

    HI, I also have a multi-configuration job and i cannot delete any job, because it shows it depends on itself or another job. But that another job also depends on some. And it doesn't give me an option to unmark the build to be kept forever. Is there some solution? (Jenkins v. 2.27)

    Thanks

  21. jenkins-infra-bot
    added
    bugFor changelog: Minor bug. Will be listed after features
    imported-jira-issue
    component:core
    resolution:fixed
    priority:critical
    component:matrix-project-plugin
    on Nov 24, 2025

  22. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original is_duplicated_by from Jira: JENKINS-11424]

  23. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original is_duplicated_by from Jira: JENKINS-12797]

  24. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    jenkins-infra-bot
    on Nov 24, 2025
    Author

    [Original relates_to from Jira: JENKINS-34723]

  25. jenkins-infra-bot
    added the
    Bug
    issue type on Nov 25, 2025
  26. jenkins-infra-bot
    removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    component:corecomponent:matrix-project-pluginimported-jira-issuepriority:criticalresolution:fixed

    Type

    Bug

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions