Nice. > new rules to the VPP Failure Cause Management database [0]
How do we manage the rules? I think the database is different from usual plugin configuration, so "Jenkins configuration as code" plugin will not help directly [5]. But I think we can manage the exported database manually in ci-management. Vratko. [5] https://issues.jenkins.io/browse/JENKINS-63773 -----Original Message----- From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Benoit Ganne (bganne) via lists.fd.io Sent: Wednesday, 2021-February-03 09:21 To: Dave Wallace <dwallac...@gmail.com>; vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] Jenkins/Gerrit Failure Cause Notifications Very nice! Do you also get statistics per failure cause? Best ben > -----Original Message----- > From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Dave Wallace > Sent: mercredi 3 février 2021 02:28 > To: vpp-dev <vpp-dev@lists.fd.io> > Subject: [vpp-dev] Jenkins/Gerrit Failure Cause Notifications > > Folks, > > Per a request by Dave Barach in the VPP Monthly Community Meeting, I > have added new rules to the VPP Failure Cause Management database [0] of > the Jenkins Build Analyzer plugin [1] to provide notifications in > gerrit/jenkins of build failure indications. The rules are applied to > the log of each Jenkins job which fails to identify the failure cause in > the build log. > > You can preview the notifications in the gerrit change [2] which I have > been using to verify that the rules work correctly. You will see the > description of the build failure cause listed on the Gerrit notification > status line. The jenkins job status page will contain links in the > "Identified problems" section of the page for each rule. > > Please note that in there is an issue with the reporting of multiple > instances of same failure contained in a build log (or maybe that is a > non-feature of the plugin). Presently only the 1st failure is listed in > the indications list on the jenkins build status page. In particular, > in the case of multiple 'make test' testcase failures [3], you will need > to search the log for any additional failures beyond one linked to in > the 'Indication 1' link [4]. > > I will continue to monitor job failures for viable failure signatures > that I can add to the . If you find a failure that you think is a good > candidate, then please directly email me the URL to the jenkins job > build status page along with the string to search for in the log and I > will add a new rule for it. > > Thanks, > -daw- > > [0] https://plugins.jenkins.io/build-failure-analyzer/ > [1] https://jenkins.fd.io/view/vpp/failure-cause-management/ > [2] https://gerrit.fd.io/r/c/vpp/+/31092 > [3] https://jenkins.fd.io/job/vpp-verify-master-ubuntu1804-x86_64/2050/ > [4] > https://jenkins.fd.io/job/vpp-verify-master-ubuntu1804- > x86_64/2050/consoleFull#-14603433817be1b593-44ad-45a7-8ca6-701783403621
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18653): https://lists.fd.io/g/vpp-dev/message/18653 Mute This Topic: https://lists.fd.io/mt/80343945/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
