test(lts): test against rc build 2.504.3

[TheMeinerLP]

Test against RC build of 2.504.3

Only for testing. Please do not merge.

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests that demonstrate the feature works or the issue is fixed

[krisstern]

@MarkEWaite are these failures okay to ignore, or do they require fixes?

[krisstern]

@jenkinsci/acceptance-test-harness-developers is it safe to ignore the failures and go ahead with an official (delayed) RC release at this stage?

[MarkEWaite]

@jenkinsci/acceptance-test-harness-developers is it safe to ignore the failures and go ahead with an official (delayed) RC release at this stage?

Yes, it is OK to proceed with the release candidate in spite of these test failures. These test failures seem to be due to a change in the job config history plugin . The job config history plugin UI overhaul released 4 days ago has caused that automated test to timeout while waiting to complete a dialog box.

A screen recording is included in the failing test result .

@mawinter69 would you be willing to investigate the changes that are needed for the saving_global_config_should_not_create_job_change acceptance test?

I'll also post that information to the issue:

• PrioritySorterPluginTest broken on main branch #2050

[mawinter69]

The failure is related to jenkinsci/job-config-history-plugin#363