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

Use git@version syntax for spack pipelines and buildcache #157

Open
cameronrutherford opened this issue Sep 3, 2024 · 1 comment
Open

Comments

@cameronrutherford
Copy link
Contributor

spack/spack#43859

spack/spack#38484 (comment)

Previously the git version feature of spack was a little buggy, and so this feature wasn't possible. Now that spack is able to handle this, we should attempt to properly version our packages in the GHCR based on the git branch.

This can also be extended to ReSolve and HiOp..

@cameronrutherford
Copy link
Contributor Author

@abhyshr I realised that the current pipelines aren't actually building new versions of ExaGO at the moment, and so they'll never fail... someone else should also take over maintainer status of ExaGO's package.py ◡̈

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