I this a general advice or are you using the warnings plugin in a different way that requires that the old behavior should be retained?
BTW: the corresponding issue is https://issues.jenkins-ci.org/browse/JENKINS-50551 > Am 05.04.2018 um 13:13 schrieb Artur Szostak <[email protected]>: > > Unless you want to make a lot of people angry, or unless there is a > fundamentally good reason, always make the existing behaviour the default. > New behaviour should be explicitly selected. If there is a good reason to > make new behaviour the default, there should at the very least be a > transition period over several plugin versions, and clear deprecation > warnings / mechanisms to allow for a sensible update / transition strategy. > > Cheers > > Artur > ________________________________________ > From: [email protected] > <mailto:[email protected]> <[email protected] > <mailto:[email protected]>> on behalf of Dan > <[email protected] <mailto:[email protected]>> > Sent: 30 March 2018 15:29:25 > To: Jenkins Users > Subject: Re: Trend Graph > > Maybe I should change that so that the first build always has no new > warnings. What do you think? I’m not sure if I break something from other > peoples’ jobs if I change that… > > This would solve my problem, so I'm all for it! > For people who want existing functionality, you could add a checkbox in > "Configure the trend graph". Although it seems my usage makes more sense, > there's probably someone who disagrees. Something like: > > > Suppress reference build > If set warnings for the reference build are not displayed as 'new' for the > graph type 'Distribution of new and fixed warnings'. > > > > Or you could reverse it and have > > Display reference build > > > On Thursday, March 29, 2018 at 7:43:19 PM UTC-4, Ullrich Hafner wrote: > I think this will not work. If no previous result is found, then an empty set > of warnings is used as baseline, so we still get a large number of new > warnings. I wonder if it would make sense to change the current behavior of > my plugin. I must admit that marking all warnings of the first build as new > is not a conscious decision. Maybe I should change that so that the first > build always has no new warnings. What do you think? I’m not sure if I break > something from other peoples’ jobs if I change that… > > The other suggestions about changing the graphs: this is currently not > supported will will never be supported with the current chart implementation. > In the future (*), I would like to replace the png server side rendered > charts with client side rendered JS charts. Then it should be easy to > configure these graphs on the client side. > > (*) Currently this is blocked by an integration of an old Prototype.JS > library in Jenkins core, see > https://issues.jenkins-ci.org/browse/JENKINS-49319 for details > > Am 29.03.2018 um 21:42 schrieb Mark Waite <[email protected] > <http://gmail.com/><javascript:>>: > > What if the first build on a branch were run without calculating warnings > (since you intend to ignore warnings from the first build, you could choose > not to compute those warnings and not to report them. > > After first build is complete, reconfigure the job (Jenkins UI or in the > Jenkinsfile if Pipeline) to report warnings. > > Mark Waite > > On Thu, Mar 29, 2018 at 12:26 PM Dan <[email protected] > <http://remcom.com/><javascript:>> wrote: > Jenkins uses a trend graph to display things like failed unit tests or > compilation warnings as a function of build number. Is there a way to > suppress only the first build OR to limit the height of the y-axis? > > My company's workflow > - create a copy of a Jenkins job for your particular branch > - Build the branch without changes. This gives a baseline for the # of > warnings in the code (it has very old code, so there are a LOT) > - The branch then automatically builds daily. New warnings introduced by the > developer show up in the Trend Graph. > > The Trend Graph is configured to show only new or fixed warnings. > The problem is that the 1st build introduces a ton of "new" warnings. This > pushes the +Y-axis max value to >1000. Any warnings fixed/introduced after > that are not visible. > > Solution > If we could somehow suppress showing just that first build, while still > showing all subsequent builds, this would be fixed. Or, if the +Y-axis could > be limited to show numbers from 0-100, this would be fixed. > > Is this possible? > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <http://googlegroups.com/><javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%40googlegroups.com?utm_medium=email&utm_source=footer> > > <https://groups.google.com/d/msgid/jenkinsci-users/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%40googlegroups.com%3Chttps://groups.google.com/d/msgid/jenkinsci-users/9449eb64-eb32-4d86-ab8f-ace4a11ff4a4%40googlegroups.com?utm_medium=email&utm_source=footer%3E>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <http://googlegroups.com/><javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGfLMfX6P_ampCegh1aKTs5uU%3D9Lt67Ag97fQApE%2BaheQ%40mail.gmail.com<https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGfLMfX6P_ampCegh1aKTs5uU%3D9Lt67Ag97fQApE%2BaheQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > > <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGfLMfX6P_ampCegh1aKTs5uU%3D9Lt67Ag97fQApE%2BaheQ%40mail.gmail.com%3Chttps://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGfLMfX6P_ampCegh1aKTs5uU%3D9Lt67Ag97fQApE%2BaheQ%40mail.gmail.com?utm_medium=email&utm_source=footer%3E>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]><mailto:[email protected] > <mailto:[email protected]>>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/ee1700ad-495b-4852-83b6-0d30063428b4%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/ee1700ad-495b-4852-83b6-0d30063428b4%40googlegroups.com?utm_medium=email&utm_source=footer> > > <https://groups.google.com/d/msgid/jenkinsci-users/ee1700ad-495b-4852-83b6-0d30063428b4%40googlegroups.com%3Chttps://groups.google.com/d/msgid/jenkinsci-users/ee1700ad-495b-4852-83b6-0d30063428b4%40googlegroups.com?utm_medium=email&utm_source=footer%3E>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/7320e864f9a741f1a75d609ec366730c%40partner.eso.org > > <https://groups.google.com/d/msgid/jenkinsci-users/7320e864f9a741f1a75d609ec366730c%40partner.eso.org>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/148B71EF-56BF-4EB8-A48A-9BC11E0AC503%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP
