Fix builds stuck loading when opening job in new Firefox tab

[AmoghParmar]

Fixes #23864

Testing done

Manually tested on Firefox by opening a job in a new tab from the Jenkins dashboard.

Before the fix, the Builds card could remain stuck on “Loading builds…” when a job
was opened in a new tab, until the tab lost and regained focus.

After the fix, builds load immediately when the job page is opened in a new tab
without requiring any tab switching.

Tested locally by running Jenkins from the built WAR.

Screenshots (UI changes only)

Before

After

Proposed changelog entries

• Fix builds remaining stuck in loading state when opening a job in a new Firefox tab

Proposed changelog category

/label bug,web-ui

Proposed upgrade guidelines

N/A

Submitter checklist

• The issue, if it exists, is well-described.
• There is automated testing or an explanation as to why this change has no tests.
• UI changes do not introduce regressions when enforcing the current default rules of Content Security Policy Plugin.

Desired reviewers

@jenkinsci/core-pr-reviewers

[AmoghParmar]

Hello Maintainerss,
I see that several CI checks are currently failing (Linux/Windows, JDK 21/25).
Could you please let me know if these failures are related to my change, or if they are known CI issues?

If they are caused by my patch, I’d really appreciate some guidance on:

• which test or area I should focus on, or
• any logs I should look at to fix this.

[MarkEWaite]

Hello Maintainerss, I see that several CI checks are currently failing (Linux/Windows, JDK 21/25). Could you please let me know if these failures are related to my change, or if they are known CI issues?

If they are caused by my patch, I’d really appreciate some guidance on:

• which test or area I should focus on, or
• any logs I should look at to fix this.

The log files from ci.jenkins.io show the issue is:

04:32:37  [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:2.0.0:corepack (prettier) on project jenkins-parent: Failed to run task: 'corepack yarn exec prettier --check .' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
04:32:37  org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal com.github.eirslett:frontend-maven-plugin:2.0.0:corepack (prettier) on project jenkins-parent: Failed to run task

That shows that you need to read the contributing guide, specifically the section that describes prettier and the section that describes yarn lint. The contributing guide describes how we maintain consistent formatting of the JavaScript code in Jenkins.

You didn't run yarn lint before submitting your pull request containing JavaScript changes. Instructions are in the contributing guide.

[AmoghParmar]

I ran the failing test locally using:

mvn -pl core -Dtest=QueueTest#testGetCauseOfBlockageForNonConcurrentFreestyle -DskipITs test

The test is not picked up locally (0 tests executed), while it fails
consistently in CI on Linux JDK 25. This appears to be related to the CI
test configuration (JUnit 4 / Vintage) rather than a local setup issue.

I’m happy to adjust the implementation or update the test if guidance is
preferred.

[MarkEWaite]

I ran the failing test locally using:

mvn -pl core -Dtest=QueueTest#testGetCauseOfBlockageForNonConcurrentFreestyle -DskipITs test

That test was a known flaky test on Windows. The fix has been merged to the master branch in pull request:

• Delete builds in QueueTest to prevent Windows test failures #26104

Pull the latest changes to your local repository, merge the master branch into this pull request, run the tests again, and push to GitHub.