[JENKINS-67028] Fix missing project hyperlink in build history

[NotMyFault]

Fixes https://issues.jenkins.io/browse/JENKINS-67028

Proposed changelog entries

• Fix missing hyperlink in build history (regression in 2.314).

Proposed upgrade guidelines

N/A

Submitter checklist

• (If applicable) Jira issue is well described
• Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade

Desired reviewers

@MarkEWaite

Maintainer checklist

Before the changes are marked as ready-for-merge:

• There are at least 2 approvals for the pull request and no outstanding requests for change
• Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
• Changelog entries in the PR title and/or Proposed changelog entries are correct
• Proper changelog labels are set so that the changelog can be generated automatically
• If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[MarkEWaite]

Thanks very much @NotMyFault ! I've tested interactively and confirmed that the hyperlink is inserted in the build history and links as expected to the build details page.

[oleg-nenashev]

Looks good to me taking the neighboring changes. Thanks for the patch!

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

[MarkEWaite]

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

Let's wait to merge this until after the Jenkins 2.319 weekly release is delivered on Thursday, Nov 4, 2021. Merging earlier won't make the fix available any sooner and delaying the merge will allow each PR submitter to handle the merge rather than placing the merge burden on the Jenkins security team.