|
Matrix jobs default to "locked" (and are difficult to delete)
------------------------------------------------------------- Key: JENKINS-10197 URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: 1.418 Reporter: tomrini Priority: Critical 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. {noformat} (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 {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150147#comment-150147 ] tomrini commented on JENKINS-10197: ----------------------------------- 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). > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: tomrini > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150400#comment-150400 ] abayer commented on JENKINS-10197: ---------------------------------- 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. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: tomrini > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150433#comment-150433 ] Gary Yund commented on JENKINS-10197: ------------------------------------- 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. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: tomrini > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150944#comment-150944 ] Barry Wark commented on JENKINS-10197: -------------------------------------- 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? > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: tomrini > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151013#comment-151013 ] Christian Höltje commented on JENKINS-10197: -------------------------------------------- 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. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: tomrini > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151014#comment-151014 ] Barry Wark commented on JENKINS-10197: -------------------------------------- Although we have the git plugin installed, all of the relevant builds are from SVN. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: tomrini > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151017#comment-151017 ] tomrini commented on JENKINS-10197: ----------------------------------- I've ran a git bisect on this problem and it's: 51c85a9fa030013553299e59649251b4f09560d5 is the first bad commit commit 51c85a9fa030013553299e59649251b4f09560d5 Author: Kohsuke Kawaguchi <[hidden email]> Date: Thu May 12 10:50:18 2011 -0700 control GC so that records are always full > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: tomrini > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Rini reassigned JENKINS-10197: ---------------------------------- Assignee: Kohsuke Kawaguchi > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151076#comment-151076 ] Christian Höltje commented on JENKINS-10197: -------------------------------------------- Yeah, that isPartial() function looks wrong.... > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151077#comment-151077 ] Christian Höltje commented on JENKINS-10197: -------------------------------------------- Link to the code in question: https://github.com/jenkinsci/jenkins/commit/51c85a9fa030013553299e59649251b4f09560d5 > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] scm_issue_link resolved JENKINS-10197. -------------------------------------- Resolution: Fixed > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151121#comment-151121 ] scm_issue_link commented on JENKINS-10197: ------------------------------------------ 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. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151122#comment-151122 ] abayer commented on JENKINS-10197: ---------------------------------- Fix will be in 1.425. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151123#comment-151123 ] dogfood commented on JENKINS-10197: ----------------------------------- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1002|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1002/] [FIXED JENKINS-10197] isPartial() check for matrix builds now only reference active configurations. Andrew Bayer : [eea67c761e78fa1b26f9d2ae82826e3e74b877ee|https://github.com/jenkinsci/jenkins/commit/eea67c761e78fa1b26f9d2ae82826e3e74b877ee] Files : * changelog.html * core/src/main/java/hudson/matrix/MatrixBuild.java > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152833#comment-152833 ] scm_issue_link commented on JENKINS-10197: ------------------------------------------ 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. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=153102#comment-153102 ] ebann commented on JENKINS-10197: --------------------------------- I'm seeing this problem in Jenkins 1.430. Isn't it "resolved" ? > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154094#comment-154094 ] Trevor Baker commented on JENKINS-10197: ---------------------------------------- Please re-open. I am seeing this behavior in 1.434 > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154107#comment-154107 ] Eric Long commented on JENKINS-10197: ------------------------------------- I am still seeing this problem in 1.424 Please re-open. > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-10197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Trevor Baker reopened JENKINS-10197: ------------------------------------ > Matrix jobs default to "locked" (and are difficult to delete) > ------------------------------------------------------------- > > Key: JENKINS-10197 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10197 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: 1.418 > Reporter: Tom Rini > Assignee: Kohsuke Kawaguchi > Priority: Critical > > 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. > {noformat} > (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 > {noformat} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira |
| Powered by Nabble | Edit this page |
