ci: print packages' timestamp in job 'install'

[umarcor]

Packages are uploaded to GCS through gsutil cp ${package} gs://${GCP_PATH}/${TIMESTAMP}/. Unfortunately, the target is hidden in the logs:

https://github.com/SymbiFlow/f4pga-arch-defs/runs/6472094719?check_suite_focus=true#step:4:24660

Copying file://symbiflow-arch-defs-xc7a50t-arty-swbut-overlay_test-11aa9fd.tar.xz [Content-Type=application/x-tar]...

Therefore, users cannot guess the URL of the arch-def packages generated by some specific commit. They know the format, they know the hash, but they don't know the specific timestamp. This PR prints it.

Ref chipsalliance/f4pga-examples#292

[mithro]

Would be great to print the full URL too?

[mithro]

Maybe a candidate for the new job summary stuff - https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/?

[umarcor]

Would be great to print the full URL too?

Since there are several URLs and all of them have a similar syntax, I don't think it's worth. The main use case is to update the date and hash used in a for loop: https://github.com/chipsalliance/f4pga-examples/pull/300/files. I.e., it's a matter of copying two values. Copying the full URL is not helpful in that case.

GitHub

docs/getting: use a for loop to wget arch-defs packages by umarcor · Pull Request #300 · chipsalliance/f4pga-examples

Example designs showing different ways to use F4PGA toolchains. - docs/getting: use a for loop to wget arch-defs packages by umarcor · Pull Request #300 · chipsalliance/f4pga-examples

[umarcor]

Maybe a candidate for the new job summary stuff - https://github.blog/2022-05-09-supercharging-github-actions-with-job-summaries/?

That's a very interesting feature! Thanks for the reference!

However, I feel it to be out of scope of this PR. I'd like to address #2675, #2676 and #2673 before generating reports/summaries.

[umarcor]

@mithro I did some tests with GITHUB_STEP_SUMMARY in hdl/containers. There seem to be issues when using composite actions, because the summaries are overwritten. See, for instance, https://github.com/hdl/containers/actions/runs/2355254788. However, it looks quite nice if the content is written from a "regular" step. Therefore, I added printing the timestamp and the hash in the summary.

GitHub

pyHDLC/run: print block titles as GHA step summary · hdl/containers@d42cbd5

Building and deploying container images for open source electronic design automation (EDA) - pyHDLC/run: print block titles as GHA step summary · hdl/containers@d42cbd5

[kgugala]

LGTM