Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Plugin style seems broken in latest on jenkins LTS

See original GitHub issue

The current plugin release lifecycle to jenkins looks odd - there are currently 12 1.13 releases, 9 of which were released in the last 4 days.

Public releases of the plugin have been observed at https://updates.jenkins-ci.org/download/plugins/build-monitor-plugin/ and https://plugins.jenkins.io/build-monitor-plugin/#releases

The latest 1.13 release builds also seems to have styling issues (at least when used with jenkins LTS). The plugin seems to be pushed to the jenkins update repo too often (and maybe some extra testing would be required)?

Thanks

Issue Analytics

State:
Created 2 years ago
Comments:5 (1 by maintainers)

Top GitHub Comments

2reactions

salavessacommented, Nov 22, 2021

Hi @jan-molak and @basil,

Thanks for the info - I can confirm that the latest release/build 1.13+build.202111220004 has fixed the styling bug initially reported.

I still believe that having such short release cycles makes it odd specially if you notice a bug in a release you just installed and when you rollback to the previous one (or update to the new latest) and the bug is still there - I ended up pretty “lost” to find a good release/version to rollback to so in my case and to be safe, I just revertd to the one from 1st October (i.e. 8 releases before the latest available by then).

Anyway, good work and thanks for the quick fix on #517

Thanks!

2reactions

basilcommented, Nov 22, 2021

@basil, @dcendents - is there any technical reason why the current continuous deployment approach should be revised?

Well, code cleanup PRs and dependency updates are generally useful to merge, but spinning a dedicated release for them and forcing users to upgrade to that release when its changelog just consists of entries like “No user-visible changes” tends to annoy users. That’s why JEP-229 ignores Dependabot PRs and code cleanup (based on label) and requires PRs to be labelled as e.g. “bug” or “RFE” for continuous deployment to kick in. This seems to have struck a chord with users.