Automated plugin release

[Marit M]

Hi,

I'm trying to create a new release, but the verify CI status fails:

Error: The log was not found. It may have been deleted based on retention settings.

https://github.com/jenkinsci/bmc-cfa-plugin/runs/5805308335?check_suite_focus=true

Can someone please have a look?

Thanks,

Marit.

[Mark Waite]

As far as I can tell, https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/ is failing to compile.  I believe that CI must pass before a release can be created

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5af0ae1a-764d-44dc-a4d5-b1eb89d9288fn%40googlegroups.com.

[Marit M]

https://github.com/jenkinsci/bmc-cfa-plugin/runs/5814524620?check_suite_focus=true

Why is it failing now?

Thanks,

Marit

ב-יום ראשון, 3 באפריל 2022 בשעה 21:14:05 UTC+3, Mark Waite כתב/ה:

[Basil Crow]

As Mark wrote in his previous message, it is because
https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/ is
failing.

[Marit M]

I fixed the build errors and it's still failing, can you please help me understand the root cause:

https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/60/console

14:23:05 ERROR: Static analysis quality gates not passed; halting early 

14:23:05 [GitHub Checks] GitHub check (name: Jenkins, status: completed) has been published.

14:23:05 Finished: FAILURE

Thanks,

Marit.

ב-יום שני, 4 באפריל 2022 בשעה 21:42:31 UTC+3, m...@basilcrow.com כתב/ה:

[Alexander Brandes]

Various Spotbugs checks are failing. Take a look at https://ci.jenkins.io/job/Plugins/job/bmc-cfa-plugin/job/main/53/spotbugs/ for the list of failures.

Locally, you can run `mvn spotbugs:check` to highlight the failures with your IDE to address them.

[Adrien Lecharpentier]

A good way would be to run

> mvn compile spotbugs:check || mvn spotbugs:gui

so that you can see the errors locally and work on them.

--

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 jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/fab3c8a1-36f7-4aed-aa59-009e033d8798n%40googlegroups.com.

[Marit M]

Did you change the quality gate?

I managed to release a version with 18 SpotBugs warnings before, and now after reducing to 7 it fails.

Thanks,

Marit.

ב-יום שלישי, 5 באפריל 2022 בשעה 19:08:07 UTC+3, adrien.lec...@gmail.com כתב/ה:

[Basil Crow]

I, too, have had trouble passing the CI quality gate checks in plugins
with existing SpotBugs violations. In my opinion, it is better to
suppress SpotBugs violations at the Maven build level (or with
@SuppressFBWarnings annotations) than at the CI level by comparing
against a baseline, since that way failures are deterministic and the
status of the local build is identical to the status of the CI build.
In core, core components, and several plugins, I have added Spotbugs
exclusions to an XML file to ensure that existing violations do not
fail the build while new violations do.