[JIRA] (JENKINS-28487) Please consider saner default for "Discard old builds"
Title: Message Title Dustin Oprea edited a comment on JENKINS-28487 Re: Please consider saner default for "Discard old builds" We all have different expectations of what's reasonable.Some of our companies are running thousands of builds per day and servicing thousands of developers and vendors with hundreds of jobs, where many people have the ability to create a ton of jobs for many purposes, where people are always coming and going over time.There will always be a percentage of jobs that don't correctly get a discard config, and, whether or not it causes a problem (which it will, when you suddenly find that very many of the jobs need to be updated to have one), we might just want to be able to specify reasonable defaults where resource-consumption is concerned.Let's try to take the position of what's helpful for users rather than what we can get away with by ignoring. This is the proper name/link for the "Create Job Advanced" plugin:https://plugins.jenkins.io/createjobadvanced Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-28487) Please consider saner default for "Discard old builds"
Title: Message Title Dustin Oprea commented on JENKINS-28487 Re: Please consider saner default for "Discard old builds" We all have different expectations of what's reasonable. Some of our companies are running thousands of builds per day and servicing thousands of developers and vendors with hundreds of jobs, where many people have the ability to create a ton of jobs for many purposes, where people are always coming and going over time. There will always be a percentage of jobs that don't correctly get a discard config, and, whether or not it causes a problem (which it will, when you suddenly find that very many of the jobs need to be updated to have one), we might just want to be able to specify reasonable defaults where resource-consumption is concerned. Let's try to take the position of what's helpful for users rather than what we can get away with by ignoring. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
