yes i will, thank you. But as fare as i see it, that only solves half of my issue.
We are seeing the job reporting "new" warnings in files that has not been change at all on the build branch, which of course is confusing the developers a lot. Which is my main problem. /Jes On 18 November 2014 11:43, Ulli Hafner <[email protected]> wrote: > The reference build is *not* used if the delta computation is deactivated. > Seems that the UI message (reference build) is show regardless of the > checkbox. Can you please file a bug report? > > > > Am 18.11.2014 um 11:38 schrieb jes Struck <[email protected]>: > > > We have a setup where we build a lot of different git branches in the same > job, to test them before merging them to master. > > When PMD, or any other warnings plugins, runs their post build task, and > reports the result they say that x warnings exceed the threshold of X > (Reference build: nnnn) > > I have configured the build to just succeed if they are equal or better > than X, and not to compare or use any reference build, actually it very > important that i do not use reference builds as that would be code in > completely different context. > > > <Screenshot 2014-11-18 11.34.03(2).png> > > Could anyone help me explain how to setup a job, so that it only valuate > if against the threshold?? > > > Just to be complety explicit my configuration is,<Screenshot 2014-11-18 > 11.36.36(2).png> > > I really would appreciate any help, thanks. > > /Jes > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
