Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
[JENKINS-53832,JENKINS-53924] - Reference the GNU C compat issues on RHEL5/ CentOS 5 in the changelog #1815
We don't have those stats.
It took more than 7 weeks to be discovered though (or 2 weeks after .1 LTS release), which indicates only a small part of the overall user base, or relatively low impact when encountered. Based on usage stats, it looks like 50+k installs of 2.136+ happened, before this was reported.
None of this screams "banner needed".
I'll merge the current PR so we have some docs, and we can look into a banner independently.
Late comment: would have been nice to have a banner or prevent the update entirely if prereq's not there in the OS. 2nd time I've done this recovery bit for this same reason too... Maybe this time I'll remember not to touch that Jenkins red box pleading with me to upgrade. I've got it running again but none of our users can log in, it's like the user DB has blown itself away somehow. Ugh.
@bharsh We discovered this after we published the release, so that's not really possible unless you're comfortable with us injecting code into your instance as part of the update check.
I encourage you to participate in LTS RC testing. Threads for it are regularly posted to the jenkinsci-dev list, e.g. https://groups.google.com/d/msg/jenkinsci-dev/Lsludh80lVM/vwG5rtCSBQAJ