[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
dogfood commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) Integrated in jenkins_main_trunk #3741 JENKINS-10197 Show keep log reason in tool tip (Revision 0f0c2a7d00c22dc9946c18b20e7f576a20cf8a86) Result = SUCCESS daniel-beck : 0f0c2a7d00c22dc9946c18b20e7f576a20cf8a86 Files : core/src/main/resources/hudson/model/Run/KeepLogBuildBadge/badge.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Daniel Beck
resolved JENKINS-10197 as Fixed
Matrix jobs default to "locked" (and are difficult to delete)
Resolving this issue as fixed again, as the concerns for which it was reopened appear to relate to current behavior that is by design.
Starting from 1.585 or so, the reason for a build to be kept forever is also shown on the tool tip of the lock icon, so it's at least easier to determine why a build is kept.
Please file a new improvement or feature request against the matrix-project component if you think the current behavior should be changed, or made configurable. You can create a bidirectional link to this issue ("More Actions" button) to establish these are related.
(Oleg: Given that this was already fixed and backported, a clean slate for the improvement seems preferable.)
Change By:
Daniel Beck
(11/Oct/14 11:20 AM)
Status:
Reopened
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Oleg Nenashev commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) @Daniel I suppose the issue could be converted to "Improvement" or closed as "Not a defect". The behavior is quite painful, but it works as designed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
SCM/JIRA link daemon commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/hudson/model/Run/KeepLogBuildBadge/badge.jelly http://jenkins-ci.org/commit/jenkins/c4df05b652b25c7bb96511e3f6e7f1467dc34a33 Log: Merge pull request #1422 from daniel-beck/JENKINS-10197 JENKINS-10197 Show keep log reason in tool tip Compare: https://github.com/jenkinsci/jenkins/compare/e518f009c515...c4df05b652b2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
SCM/JIRA link daemon commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Run/KeepLogBuildBadge/badge.jelly http://jenkins-ci.org/commit/jenkins/0f0c2a7d00c22dc9946c18b20e7f576a20cf8a86 Log: JENKINS-10197 Show keep log reason in tool tip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Daniel Beck commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) Is there an actual bug left to resolve here (rather than an RFE)? I mean, it's quite obvious from e.g. Jesse's comment on 27/Mar/13 that the behavior Courtney Sims describes is intended. Alexander Artemov unfortunately provided no further details what exactly he's seeing for this to be reopened, but it may well be the same. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Oleg Nenashev updated JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) Assigned the issue to "matrix-project" Change By: Oleg Nenashev (16/Jun/14 1:49 PM) Component/s: matrix-project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Courtney Sims updated JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) Change By: Courtney Sims (16/Jun/14 1:46 PM) Attachment: jenkins-matrix-builds.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Courtney Sims commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) This is still an issue in version 1.550. We have a matrix job where often only one column of configurations is built in a single build. The next time the job is run, a different column might be built, and then the previous build gets locked, I'm assuming because it's being referenced (as "skipped") in the new build. But what this means for our matrix job is that almost every single build ends up locked. I would like to be able to unlock these builds so that I can delete them. Rather than forcing a build to be implicitly locked because it's being referenced in a later build, why can't the reference be removed/updated if the build is deleted? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Oleg Nenashev edited a comment on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) The issue appears in 1.509.4 as well. It also leads to the infinite disk usage if a job has timeouts or disabled configs. It makes sense to add an option, which disables such linking. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10197) Matrix jobs default to "locked" (and are difficult to delete)
Oleg Nenashev commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) The issue appears in 1.509.4 as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
