-
Notifications
You must be signed in to change notification settings - Fork 81
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
Extend project development infrastructure documentation #1105
Comments
@neumantm the docker container is created for us by an external collaborator in the E4S project. @eugeneswalker will you provide the link to the correct repo that contains the definition? Essentially it is just a base ubuntu image with a [email protected] pre-installed. We then use spack-manager to install The CI re-uses all the TPLS and then just rebuild nalu-wind, and we only run the unit-tests. I'd like to add in a subset of regression tests at some point too, but we currently don't store up-to-date golds in the repo so we'd need to update that process for the CI. That static analysis right now is only doing a style check of the cpp code and doesn't check docs. We are using clang-format from clang@13 for our style checks. Improving the CI is definitely something on the todo list so if you want to contribute there we'd be more than happy to have the assistance 😁. |
The Dockerfile and CI are here: This runs once a day, in the morning, and generates the exawind-snapshot container image and pushes it to DockerHub. |
Thank you for this infos. |
@ajpowelsnl this is the docker container you should look at to see how we use spack-manager. I gave you the wrong link in our meeting the other day. |
Hi @psakievich, @jrood-nrel -- Thanks! I'll look into getting this info into the working base image on Perlmutter. |
As an external contributor I'd appreciate to have more documentation about the existing software development infrastructure.
This would help understanding how things work and what is going on.
Specific points I'm thinking about:
The text was updated successfully, but these errors were encountered: