[JENKINS-53179] Extend env variable to facilitate the access to the BO URLs

[v1v]

JENKINS-53179

Enable URLs for a page that displays tests and artifacts for a Run.

Depends on jenkinsci/display-url-api-plugin#25

Highlights

• RUN_ARTIFACTS_DISPLAY_URL points out to the qualified URL for a page that displays artifacts for a Run
• RUN_TESTS_DISPLAY_URL points out to the qualified URL for a page that displays tests for a Run

UI

node {
    sh 'env | grep -i display_ | sort | tee file.txt'
    archive 'file.txt'
}

@jenkinsci/code-reviewers

[v1v]

TODO: Change the version with the incremental one

[v1v]

As long as jenkinsci/display-url-api-plugin#26 is merged then jenkinsci/display-url-api-plugin#25 will generated an incremental artifact which could be used in this case

[abierbaum]

@v1v @jglick Was just looking for something exactly like this today. Any chance to get through through and into the plugin?

[StevenGiguere76]

Anything this patch needs before it can be merged in? Lots of articles pointing to the fact it needs to be solved, has been, but hasn't been pushed fully into the plugin?

[v1v]

Need to address some of the concerns in jenkinsci/display-url-api-plugin#25 in order to move forward

[FallDownT]

Is anything still needed for this patch to be merged in? This feature would be extremely useful to me right now and it seems ready to merge.

[v1v]

I'm just a contributor, the maintainer is the one to review this PR and merge if happy with

[v1v]

@jenkinsci/code-reviewers this PR has been stalled for a year or so, any feedback?

[olamy]

@v1v can you please rebase? I would prefer a released version of https://github.com/jenkinsci/display-url-api-plugin but that's my job to do it I guess ;)

[jglick]

I would prefer a released version of https://github.com/jenkinsci/display-url-api-plugin but that's my job to do it I guess

Certainly this should not be merged while referring to an incremental dependency version. What I have done in the past as a plugin maintainer, or recommended other maintainers do: release the upstream plugin, then use GH suggest changes to guide the downstream PR author to switch to the new release version. At that point downstream is safe to merge & release. (No need for the PR author to rebase; maintainer can always squash-merge if they enjoy destructive history operations.)

[olamy]

@v1v version 2.3.3 done please update your pull request thanks

[jglick]

(plus merge conflict resolution)

[timja]

@olamy or @jglick could this be released please?

[olamy]

@timja oh yes I will do it early next week

[syl20bnr]

@olamy When do you have time to release the version 2.4 of the plugin ?

[olamy]

@syl20bnr all done buddy
@timja sorry for delay

[syl20bnr]

Thank you ! 💯