Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exposing build information in a more intuitive and useful way #125

Open
aidanheerdegen opened this issue Sep 15, 2024 · 0 comments
Open

Comments

@aidanheerdegen
Copy link
Member

There is a build DB that tracks all deployed builds

https://dev.access-hive.org.au/release-provenance

but it would also be useful, and relatively straightforward, to provide an informative web-page for a deployment that has click-able links to all the relevant spack packages, and the specific versions of the code referenced.

Links to builtin spack packages should link to the relevant entry in packages.spack.io, e.g.

https://packages.spack.io/package.html?name=netcdf-c

and access-nri packages should either resolve to the package file in the access-nri/spack-packages repo, or to an access-nri equivalent of packages.spack.io

The web page could be rendered by an actions workflow to a github.io page, and even PRs could see an updated preview using an action like deploy-pr-preview.

This could address some of the problems people have understanding what the various parts of the spack.yaml refer to, and help with making it clear what versions of code are referred to, see ACCESS-NRI/ACCESS-OM3#5 (comment)

The layout of the page is could be something that looks a bit like packages.spack.io, or it could be the spack.yaml but with the various parts clickable through to the relevant code etc, maybe tooltip highlights to explain what each part does? The latter would be a lot more complex, and likely not something worth implementing immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant