-
Bug
-
Resolution: Not A Defect
-
Major
-
Jenkins Version 2.225
-
Powered by SuggestiMate
The enable auto refresh button has been missing since the last update.
Without this function there is a memory problem on our server.
- jenkins.png
- 67 kB
- jenkins.png
- 57 kB
[JENKINS-61592] Enable auto refresh button os missing
Was the function removed because the refresh-function from the browser should be used instead, or that Jenkins now always keeps is screens up-to-date?
erwindon2 The former, over the long term we want to get to the latter. Implementation-wise it's always been a mess, and the option wasn't used all that much.
Hmm... was this feature causing harm? If not, I am not sure why it was removed. Even if few people use it, they do use it. I use it when I need timely info on when builds are complete/promoted. I don't want to keep refreshing the page to see this.
I agree you should be doing this seamlessly on the page, but until that is developed, can you please bring back the autorefresh button?
Thanks.
Why was this feature removed? After updating our windows Jenkins service the option was gone and considered a bug and rolled back to the previous version because of his.
Please can it be brought back? Maybe as a plugin?
Many Thanks.
Cannot really be done in a plugin.
Use a Wall Display / Radiator type Jenkins plugin to get a self-updating view, or install a browser addon to reload pages periodically.
Curious about "the option wasn't used all that much.". Not a large sample size, but everyone I know uses the feature. Weird to have a bunch of progress bars that just sit there not updating. The feature certainly has had its issues, but recently it has become significantly more stable and useful (last 12 months or so)
also, side note that browser extensions/plugins are often blocked by corporate policies so that option is not 100% viable.
Curious about "the option wasn't used all that much.".
Jenkins, unless opted out, collects some limited usage statistics and telemetry. For this feature, we collected data from October to December 2019, and less than 5% of users used the feature. (And it looks like I was the only one who wanted to bother with doing that, most other core contributors told me to just delete it already.)
Re progress bars not moving – if they're supposed to, that's a bug, otherwise a legitimate, useful feature request. Ideally we'll get to where all views have some individually updating elements to let people know about changes.
@Daniel,
Thanks for that feedback. That is actually much more scientific than my "feels like everyone uses that". The progress bars that don't seem to work anymore are those after clicking an in progress build number. But honestly, people probably don't go to that page a lot to watch the status, especially with the advent of pipelines and such.
I am one of the 5% wondering where this feature went to.
The status icons do not otherwise auto-refresh which can be very misleading and confusing. Is there a way to solve that?
I am missing this feature as well. There are two areas that mostly don't update. I say mostly, cuz seemingly randomly they do update once in a while. I've circled the areas that i've noticed in the image below. The flashing blue dot icon never updates after it starts flashing. The builds listed in the executor list update sometimes and other times they don't. I can live without the auto refresh button, as long as things update when they should so you don't have to keep hitting refresh on the browser if you're actively watching the page.
FYI, i'm currently on 2.227.
Joe
The same her. To activate the auto refresh feature was the 1st thing we learned in the Jenkins training many years ago. Is there a alternativ? Without an up-to-date overview of the status of all jobs, the landing page is pointless.
Same for me, sometimes I don't see updating correctly, or even the job timestam looks odd. I must always refresh twice the page for MultiJobs.
Same issue exists for me since the refresh was deactivated. Always I must refresh twice the page in order to get last status correctly.
This is not a bug. The feature will not be restored. Please leave this issue closed.
As I wrote above, individual changes elsewhere to update status information in the background is what should be done.
Bonus: If your Jenkins instance is configured to not submit anonymous usage statistics to the Jenkins project, you only have yourself (or your admin) to blame.
Cool response. You guys really know how to treat paying customers. We all know what should be done, but that doesn't change the fact that you aren't doing it (or haven't yet anyway). You seemed to hint that there was a technical reason for removing the old refresh feature without replacement, so perhaps it would make sense to us 5 percenters if you just explained that.
You guys really know how to treat paying customers.
I don't understand this comment. Jenkins is free software distributed under the MIT license.
If you're referring to my employer's products or services, I recommend you go through CloudBees support and feedback systems for customers. That could help prioritize support for dynamic refresh of components that are important to you.
But this site is the Jenkins project's issue tracker, not CloudBees's.
there was a technical reason for removing the old refresh feature
JENKINS-19828 and linked issues should give you an idea of various problems with auto refresh. While many of these individual problems may have been addressed since, it's not become a better designed solution since JENKINS-484 was filed in 2007.
This feature has been removed without replacement.
Please report the memory problem and provide information allowing maintainers to investigate it.