When I created a new jenkins app, when logged in I see the following message: > New version of Jenkins (1.472) is available for download. AFAIK user can't upgrade jenkins at will so such messages should be suppressed from the UI.
We also need to upgrade jenkins to resolve 823837 - that would temporarily fix this and revolve the other
Patch introduced to disable the Jenkins update checks.
Fixed with: https://github.com/openshift/crankcase/pull/199
Checked on latest stage, create jenkins server and visit the jenkins console, walkthrough it, no such warning appears.
Do notifications on new plug-in versions still work?
Sorry for the missing check, after click the 'Check now' in the Update Center, the "New version of Jenkins (1.474) is available for download (changelog). " appears. Assign this bug back.
The original bug description was to suppress the *automatic* update warning that was appearing. The patch in place correctly suppresses the automatic warning by disabling automatic update checking. Of course, if the user explicitly invokes update checks, they will be told whether or not a new version is available. This is expected as they actively checked through an explicit UI interaction, and the patch in place doesn't remove Jenkins' ability to check for updates, it merely configures it from an automation standpoint. If there really is a requirement to somehow rip out the automatic update component of Jenkins, please open a new bug specifically for that use case. I am not sure it's possible to outright remove the automatic update checking component without maintaining our own custom version of Jenkins. If altering the Jenkins distribution itself would be required, we'd have to open a story to evaluate the effort and sanity of such an approach. In any case, this particular bug is resolved, and let's talk about the requirements for the newly discovered use case before re-opening this bug. Thanks.
Well I believe user should not be bugged by such warnings that he/she can do nothing to remove. If there is a switch to enable updates for core jenkins and that is turned off by default, then fine, if user enables that, then its not our problem. It just doesn't feel polished to see errors and warnings about things you can do nothing about and are not a real problem.
As devel and reporter's comments. Mark this bug as verified.
Eh, I think this is now a new bug (one should probably be opened for it). But even with that, it almost seems like we'd have to patch jenkins in order to fix it and I'm not so sure we should be in the business of doing that at the moment. I think the user clicking check now is an action outside of our control but it's worth investigation. Perhaps just in a new low priority bug.