Enable release image building

[yzhang-23]

PR Type

• [ ] Breaking change
• [X] Feature
• [ ] Patch

Brief Description Enable installating of a repo after its successful building, then build a docker image for the installed library and push it to the nwchemex-project registry.

Not In Scope

PR Checklist

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

TODOs

• [X] Write the action files.
• [X] Test the actions on my forked branches.

[yzhang-23]

On second thought, this is going to be a huge change to our CI. We should probably setup a dummy organization and iron out all the kinks in an end-to-end solution before pushing them to the NWX org.

I agree. How to copy the entire organization to a new one?

[ryanmrichard]

On second thought, this is going to be a huge change to our CI. We should probably setup a dummy organization and iron out all the kinks in an end-to-end solution before pushing them to the NWX org.

I agree. How to copy the entire organization to a new one?

I don't think you need to copy the whole org, just .github, ParallelZone, and PluginPlay. Once you have those going that should be 99% of the battle.

[yzhang-23]

On second thought, this is going to be a huge change to our CI. We should probably setup a dummy organization and iron out all the kinks in an end-to-end solution before pushing them to the NWX org.

I agree. How to copy the entire organization to a new one?

I don't think you need to copy the whole org, just .github, ParallelZone, and PluginPlay. Once you have those going that should be 99% of the battle.

Ok, I think I have already created an organization for CI testing, just trying to put my forked branches of .github, ParallelZone and PluginPlay into it.

[ryanmrichard]

On second thought, this is going to be a huge change to our CI. We should probably setup a dummy organization and iron out all the kinks in an end-to-end solution before pushing them to the NWX org.

I agree. How to copy the entire organization to a new one?

I don't think you need to copy the whole org, just .github, ParallelZone, and PluginPlay. Once you have those going that should be 99% of the battle.

Ok, I think I have already created an organization for CI testing, just trying to put my forked branches of .github, ParallelZone and PluginPlay into it.

You should be able to fork the repos as the organization you're trying to put them in.

[yzhang-23]

On second thought, this is going to be a huge change to our CI. We should probably setup a dummy organization and iron out all the kinks in an end-to-end solution before pushing them to the NWX org.

I agree. How to copy the entire organization to a new one?

I don't think you need to copy the whole org, just .github, ParallelZone, and PluginPlay. Once you have those going that should be 99% of the battle.

Ok, I think I have already created an organization for CI testing, just trying to put my forked branches of .github, ParallelZone and PluginPlay into it.

You should be able to fork the repos as the organization you're trying to put them in.

Got it. Now all 3 repos are in my CI-test organization.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: yzhang-23
:x: Yu Zhang

---

Yu Zhang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[yzhang-23]

Ok, I see. Let me make the image-based CI workflow working for PluginPlay and ParallelZone in my own CI-testing organization, then think about merging. I will try to follow the design in #105. Now not all the issues in #105 have been addressed in my planned solution, but I will refine it. Thanks!

[ryanmrichard]

Ok, I see. Let me make the image-based CI workflow working for PluginPlay and ParallelZone in my own CI-testing organization, then think about merging. I will try to follow the design in #105. Now not all the issues in #105 have been addressed in my planned solution, but I will refine it. Thanks!

I think that's a start, but there's more complexity in play when you get further along. Notably the dependency diamond problem (package A is used by packages B and C; package D then depends on packages B and C and thus depends on A through both B and C).