Failing lcov is making the whole ci/cd pipeline to fail. To make things more flexible, a Dockerfile is split to three different files, where one is responsible for building the project, another takes care of unit testing and third one document generation. Lcov is disabled for now, but it can be easily added later on using a separate Dockerfile.lcov if needed.
Later on, we can also extend this with Dockerfile.deploydocs or similar which takes care of deploying documentation to a some cdn, as well as have separate Dockerfile.release which gets triggered just for tagged versions, which automatically pushes tested containers to DockerHub/SingularityHub.
Failing lcov is making the whole ci/cd pipeline to fail. To make things more flexible, a Dockerfile is split to three different files, where one is responsible for building the project, another takes care of unit testing and third one document generation. Lcov is disabled for now, but it can be easily added later on using a separate
Dockerfile.lcovif needed.Later on, we can also extend this with
Dockerfile.deploydocsor similar which takes care of deploying documentation to a some cdn, as well as have separateDockerfile.releasewhich gets triggered just for tagged versions, which automatically pushes tested containers to DockerHub/SingularityHub.Closing #29.