Possible improvements for CI/CD workflow

[mayrmt]

Description

PR #113 adds a first implementation of a CI/CD workflow using a docker container to be executed on GitHub-hosted hardware. Its design is basic, so that we can it to work quickly, yet the following items might be improved over time.

Possible Solution and Definition of Done

• Change the "namespace" the docker container in the GitHub Container Registry (GHCR) from @RShaw026's personal space to the imcs-compsim space, so that the GHCR space matches the organization, that owns the MIRCO repository.
• Automate the creation/update and deployment of the docker container via a GitHub workflow (instead of the currently fully manual process).
• [ ]

Related Issues and Merge Requests

• Follows Broken CI/CD workflow #111, PR Add CI/CD on GitHub #113

[isteinbrecher]

I suggest to use the 4C docker container, it already has all the required dependencies installed and there is no additional effort in providing an own MIRCO container.

[mayrmt]

With MIRCO being a stand-alone project and having use cases outside of 4C, I'd rather not depend on 4C.

The 4C dependencies are rather heavy. MIRCO only requires Trilinos/Teuchos at the moment and is about to replace this dependency by a dependency on plain Kokkos & KokkosKernels (without Trilinos).

[RShaw026]

I agree with @mayrmt. The current MIRCO dependency is very light, and it is a stand-alone project.