Build/test/release with a container action

[yzhang-23]

PR Type

• Breaking change
• Feature
• Patch

Brief Description
This PR is about to build/test/release ParallelZone with the pre-built base image. The workflow starts at checking whether the base image needs to be re-built or not. Once the base image is ready, it is used to build a temporary building image (base + release images of dependent repos. Note: here ParallelZone has no dependent repo, however, for consistency we still "build" the building image which is identical to the base image. For other repos the building image might be different from the base images.). The key step of building/testing/releasing happens in a container created from this temporary building image, which is not necessary to save. If the building and testing processes are successful, finally two release images for gcc and clang would be pushed into the GitHub registry for future use.
The container action for building/testing/releasing here provides a template for developing similar actions for other repos.

Not In Scope

Now the version no. of necessary tools (e. g., gcc) and packages are manually provided in the workflow files. This information will be retrieved from files in NWXCmake through a workflow. I'm working on that.

PR Checklist

• Is documented
• Is tested
• Adheres to applicable organization standards

TODOs

• Write a workflow to obtain the package version info from the file.

[yzhang-23]

The workflow build_base.yaml will be called if any of the relevant docker files has been changed.

[ryanmrichard]

No actions seem to have run.

[ryanmrichard]

Is it possible to move the actions/ directory into the .github/ directory? I can go either way on the Dockerfile directory (assuming it can be used to build Docker images outside of CI/CD). Basically I want to keep the CI/CD stuff together and not contaminate the top-level directory any more than we need to.

[yzhang-23]

Is it possible to move the actions/ directory into the .github/ directory? I can go either way on the Dockerfile directory (assuming it can be used to build Docker images outside of CI/CD). Basically I want to keep the CI/CD stuff together and not contaminate the top-level directory any more than we need to.

Here the question is this type of container actions are adapted to the specific repos they take care of (everything must be happen in the same container, no separated steps), so I think it is not good to place them in .github, although I definitely want to do that. I will also welcome any better solutions.

[ryanmrichard]

Is it possible to move the actions/ directory into the .github/ directory? I can go either way on the Dockerfile directory (assuming it can be used to build Docker images outside of CI/CD). Basically I want to keep the CI/CD stuff together and not contaminate the top-level directory any more than we need to.

Here the question is this type of container actions are adapted to the specific repos they take care of (everything must be happen in the same container, no separated steps), so I think it is not good to place them in .github, although I definitely want to do that. I will also welcome any better solutions.

To be clear I'm talking about the .github/ directory in this repo, not the .github repo.

[yzhang-23]

Is it possible to move the actions/ directory into the .github/ directory? I can go either way on the Dockerfile directory (assuming it can be used to build Docker images outside of CI/CD). Basically I want to keep the CI/CD stuff together and not contaminate the top-level directory any more than we need to.

Here the question is this type of container actions are adapted to the specific repos they take care of (everything must be happen in the same container, no separated steps), so I think it is not good to place them in .github, although I definitely want to do that. I will also welcome any better solutions.

To be clear I'm talking about the .github/ directory in this repo, not the .github repo.

I'm sorry for misunderstanding your point! Definitely this action and the Dockerfile/ directory can be moved under .github of this repo.

[ryanmrichard]

It occurs to me that this workflow (and also the current workflow) aren't building and running the Python tests. I'm fine merging this before it can run the Python tests, but I think we should fix that before going further down the stack.

[yzhang-23]

It occurs to me that this workflow (and also the current workflow) aren't building and running the Python tests. I'm fine merging this before it can run the Python tests, but I think we should fix that before going further down the stack.

So, in order to run the python tests, do we need to turn on BUILD_PYBIND11_PYBINDINGS and add cmaize_add_tests() entries in the CMakeList.txt file?

[ryanmrichard]

It occurs to me that this workflow (and also the current workflow) aren't building and running the Python tests. I'm fine merging this before it can run the Python tests, but I think we should fix that before going further down the stack.

So, in order to run the python tests, do we need to turn on BUILD_PYBIND11_PYBINDINGS and add cmaize_add_tests() entries in the CMakeList.txt file?

The various CMakeLists.txt files should already be setup, so yes it's mainly turning on BUILD_PYBIND11_PYBINDINGS and then dealing with the additional Python dependencies (mainly Python itself, but also some PyPI packages)

[yzhang-23]

The various CMakeLists.txt files should already be setup, so yes it's mainly turning on BUILD_PYBIND11_PYBINDINGS and then dealing with the additional Python dependencies (mainly Python itself, but also some PyPI packages)

Tried turning on BUILD_PYBIND11_PYBINDINGS and installed pybind11. However, the tests py_parallelzone and test_pz_under_mpi failed on my lcal machine.

[ryanmrichard]

The various CMakeLists.txt files should already be setup, so yes it's mainly turning on BUILD_PYBIND11_PYBINDINGS and then dealing with the additional Python dependencies (mainly Python itself, but also some PyPI packages)

Tried turning on BUILD_PYBIND11_PYBINDINGS and installed pybind11. However, the tests py_parallelzone and test_pz_under_mpi failed on my lcal machine.

I'd merge this PR before worrying about getting the Python tests to work.

[yzhang-23]

The various CMakeLists.txt files should already be setup, so yes it's mainly turning on BUILD_PYBIND11_PYBINDINGS and then dealing with the additional Python dependencies (mainly Python itself, but also some PyPI packages)

Tried turning on BUILD_PYBIND11_PYBINDINGS and installed pybind11. However, the tests py_parallelzone and test_pz_under_mpi failed on my lcal machine.

I'd merge this PR before worrying about getting the Python tests to work.

Sure. That's just my testing try.

[ryanmrichard]

🚀 [bumpr] Bumped! New version:v0.1.10 Changes:v0.1.9...v0.1.10