feat(publishBuildStatusReport): publishes controller job status on reports.jenkins.io

[jayfranco999]

As per - jenkins-infra/helpdesk#2843 (comment)

publishBuildStatusReport will publish the build status report on reports.jenkins.io using pre-existing publishReports shared library script.

Once completed we can move on to the next phase of monitoring the reports.

Testing with jenkins-infra/docker-404#46

[dduportal]

Unit tests are missing :)

[jayfranco999]

Update:

Added unit tests.

[jayfranco999]

Update:

Added a dir block to execute az copy commands in context of current directory in the agent. The report was generated in the expected path

https://builds.reports.jenkins.io/build_status_reports/infra.ci.jenkins.io/docker-jobs/docker-404/PR-46/status.json

Code clean-up has been performed for the pipeline script and the test suite.

principal branch check will be uncommented once approved.

[dduportal]

Thanks @jayfranco999 . The code still have many things to review: it works but it is really verbose for not a lot of values (LLM generated?) which adds a lot of complexity and instructions.

As a general rule of thumb: the less you do in Pipeline (e.g. Groovy), the safer we are.
You should always aim at running one sh step and build thing around it (such as the required withEnv() wrapping).

=> A good start would be to remove the utility function for parsing Date and time, adn group the sh into a single step.

Don't hesitate to use my suggestions as starters

[dduportal]

You have to intercept failures and collect logs (archiveArtfiacts) with the same technique as in Good idea. However you also need to collect the logs if the sh step (otherwise you don't need to collect azcopy logs).

We accept the simplification of saying: "either it succeeds or it fails. IF it fails, collect and archive logs)

[dduportal]

@Art39print please stop spamming us or you'll be blocked.

[dduportal]

LGTM! We tested all cases on jenkins-infra/docker-404 and it works as expected: https://builds.reports.jenkins.io/build_status_reports/infra.ci.jenkins.io/docker-jobs/docker-404/main/status.json