[JENKINS-75259] Job start time and remaining time gone from root build history widget for freestyle jobs

[jenkins-infra-bot]

Hi,

  After updating Jenkins from version 2.4793 to 2.492.1, we noticed that the message which pops up when one hovers the mouse on the running job status bar now only shows "Pending" message as compare to "Start x hr y min ago" ( see the attached pics). This message was very helpful to identify the jobs which are taking long time. Now after moving to version 2.492.1 , one has to click on the build to actually see for how long it is running.

The previous popup was very helpful, can you please revert this change?

 

Thanks,

--Shahzad

---

Originally reported by smuzaffar, imported from: Job start time and remaining time gone from root build history widget for freestyle jobs

• assignee: mawinter69
• status: Closed
• priority: Minor
• component(s): core
• label(s): 2.492.2-fixed, regression, ux
• resolution: Fixed
• resolved: 2025-02-13T18:10:19+00:00
• votes: 0
• watchers: 3
• imported: 2025-11-24

Raw content of original issue

Hi,

  After updating Jenkins from version 2.4793 to 2.492.1, we noticed that the message which pops up when one hovers the mouse on the running job status bar now only shows "Pending" message as compare to "Start x hr y min ago" ( see the attached pics). This message was very helpful to identify the jobs which are taking long time. Now after moving to version 2.492.1 , one has to click on the build to actually see for how long it is running.

The previous popup was very helpful, can you please revert this change?

 

Thanks,

--Shahzad

environment

AlmaLinux 9<br/>
Jenkins 2.492.2

7 attachments

• build-2.png

  

• build-3.png

  

• build-4.png

  

• build-5.png

  

• jenikins-2.479.3.jpeg

  

• jenkins-2.492.1.jpeg

  

• start-time-and-estimated-completion.png

  

[jenkins-infra-bot]

• Remote links associated with this issue:

  • Culprit: PR-9749
  • Fix: PR-10259

[jenkins-infra-bot]

smuzaffar:

• Original comment link
• Raw content of original comment:

  also in version 2.479.3, when one clicked on the status bar then it opened the job console page now clicking on status bar opens the project page instead of the actual build console page
  

also in version 2.479.3, when one clicked on the status bar then it opened the job console page now clicking on status bar opens the project page instead of the actual build console page

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I can't duplicate the issue that you're showing in your photos.  We'll need more information to duplicate the issue.  When I open the Jenkins core job, I see the following when I hover over the running build:
  
    
  
  I'm running Google Chrome 133.0.6943.60 and Microsoft Edge 133.0.3065.59 and Firefox 135.0 on Windows 11.  The progress reporting hover works as expected from all of them when accessing the job history.
  
  Maybe you're looking at a different page than I'm checking?
  
  Maybe you're using an older browser than I am using?
  
  Maybe you're using a reverse proxy between Jenkins and your web browser and there is a configuration issue in the reverse proxy?
  

I can't duplicate the issue that you're showing in your photos. We'll need more information to duplicate the issue. When I open the Jenkins core job, I see the following when I hover over the running build:

I'm running Google Chrome 133.0.6943.60 and Microsoft Edge 133.0.3065.59 and Firefox 135.0 on Windows 11. The progress reporting hover works as expected from all of them when accessing the job history.

Maybe you're looking at a different page than I'm checking?

Maybe you're using an older browser than I am using?

Maybe you're using a reverse proxy between Jenkins and your web browser and there is a configuration issue in the reverse proxy?

[jenkins-infra-bot]

mawinter69:

• Original comment link
• Raw content of original comment:

  I  can duplicate the problem but it only affects freestyle jobs. Pipeline jobs implement  executorCell.jelly and that behaves differently obviously
  

I  can duplicate the problem but it only affects freestyle jobs. Pipeline jobs implement  executorCell.jelly and that behaves differently obviously

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I can't duplicate it with a freestyle job on weekly.ci.jenkins.io. I ran https://weekly.ci.jenkins.io/job/folder/job/freestyle/ with a 37 second sleep in a shell step. All of the samples show when the job started.  The last run shows the estimated time to completion.  I assume that is because there is enough data at that point for Jenkins to estimate time to completion.
  
  The results looked like this:
  
  Second run with 37 second sleep
  
  
  Third run with 37 second sleep
  
  
  Fourth run with 37 second sleep
  
  
  Fifth run with 37 second sleep
  
  
  

I can't duplicate it with a freestyle job on weekly.ci.jenkins.io. I ran https://weekly.ci.jenkins.io/job/folder/job/freestyle/ with a 37 second sleep in a shell step. All of the samples show when the job started. The last run shows the estimated time to completion. I assume that is because there is enough data at that point for Jenkins to estimate time to completion.

The results looked like this:

Second run with 37 second sleep

Third run with 37 second sleep

Fourth run with 37 second sleep

Fifth run with 37 second sleep

[jenkins-infra-bot]

mawinter69:

• Original comment link
• Raw content of original comment:

  This affects the executors widget on the main dashboard not the job page itself
  

This affects the executors widget on the main dashboard not the job page itself

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  This affects the executors widget on the main dashboard not the job page itself
  
  Thanks!  I should have detected that from the pictures that were included.
  

This affects the executors widget on the main dashboard not the job page itself

Thanks! I should have detected that from the pictures that were included.

[jenkins-infra-bot]

smuzaffar:

• Original comment link
• Raw content of original comment:

  thanks mawinter69  for looking in to it. I confirm that issue is with "executors widget" on the main dashboard and yes all our jobs are based on freestyle jobs. I also confirm that job time information on the job page itself works.
  
  Thanks, --Shahzad 
  

thanks mawinter69  for looking in to it. I confirm that issue is with "executors widget" on the main dashboard and yes all our jobs are based on freestyle jobs. I also confirm that job time information on the job page itself works.

Thanks, --Shahzad 

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  smuzaffar it would be a nice help for the Jenkins project if you could download the incremental build of the pull request from Markus and run it in a small test to confirm that it resolves your issue.
  
  I've confirmed that it resolves the issue in my test.
  

smuzaffar it would be a nice help for the Jenkins project if you could download the incremental build of the pull request from Markus and run it in a small test to confirm that it resolves your issue.

I've confirmed that it resolves the issue in my test.

[jenkins-infra-bot]

smuzaffar:

• Original comment link
• Raw content of original comment:

  Hi,
  
    I confirm that using the latest jenkins-war from https://github.com/jenkinsci/jenkins/pull/10259/checks?check_run_id=37059490246 has fixed both issues
  
  	
  Job start time and remaining estimate now works for freestyle project on the executors widget on the main dashboard
  	
  Clicking on the status bar via the executors widget on the main dashboard takes you to the console page of the build
  
  
  
  Thanks,
  
  --Shahzad
  

Hi,

  I confirm that using the latest jenkins-war from https://github.com/jenkinsci/jenkins/pull/10259/checks?check_run_id=37059490246 has fixed both issues

• Job start time and remaining estimate now works for freestyle project on the executors widget on the main dashboard
• Clicking on the status bar via the executors widget on the main dashboard takes you to the console page of the build

Thanks,

--Shahzad

[jenkins-infra-bot]

smuzaffar:

• Original comment link
• Raw content of original comment:

  Another UI difference between 2.479.3 and 2.492.1 is that when I click on "Retry" ( link on the left panel of build) for a failed build then previously I there was a popup with message "Done" but now there is no popup and one does not know if "retry" was done or not. Let me know if I should open a separate issue/ticket for this?
  

Another UI difference between 2.479.3 and 2.492.1 is that when I click on "Retry" ( link on the left panel of build) for a failed build then previously I there was a popup with message "Done" but now there is no popup and one does not know if "retry" was done or not. Let me know if I should open a separate issue/ticket for this?

[jenkins-infra-bot]

mawinter69:

• Original comment link
• Raw content of original comment:

  Please open a new bug. This affects the rebuild and naginator plugins, but the root might be a change in core. For the build now button the behaviour was changed from that small popup to a more visible notification at the screen bottom. Maybe this has also an effect on those 2 plugins
  

Please open a new bug. This affects the rebuild and naginator plugins, but the root might be a change in core. For the build now button the behaviour was changed from that small popup to a more visible notification at the screen bottom. Maybe this has also an effect on those 2 plugins

[jenkins-infra-bot]

mawinter69:

• Original comment link
• Raw content of original comment:

  found the issue already opened a new bug JENKINS-75265
  

found the issue already opened a new bug JENKINS-75265