The docker-compose.yml in Broadsea makes use of a number of OHDSI containers:
Container
Reference
Owner
ohds/broadsea-hades
4.2.1
Anthony Sena
ohdsi/webapi
latest
???
ohdsi/atlas
latest
???
ohdsi/broadsea-atlasdb
2.0.0
???
I'd like to propose the following approach for managing the latest development build of a container ("latest") vs. a tagged version of a container ("released"):
The "latest" build of a container should reflect the most recent pre-released version of the corresponding repository. For example, "ohdsi/hades" should reflect the contents of the develop branch and use the most recent version.
The "released" build of a container should correspond to a tagged release of the corresponding repository.
Additionally, we should be using GitHub Actions (GHA) to manage the build and publishing of containers to the OHDSI DockerHub. GHA should be used to manage both the "latest" and "released" builds.
Somewhat related (and if not we can spin up a new issue): the "ohdsi/braodsea-hades" container should be replaced by an "ohdsi/hades" container that is defined by a GHA in https://github.com/OHDSI/Hades.
Tagging @leeevans to try and make sure I've summarized our discussion. Also tagging @alondhe, @konstjar, @ablack3
The
docker-compose.ymlin Broadsea makes use of a number of OHDSI containers:I'd like to propose the following approach for managing the latest development build of a container ("latest") vs. a tagged version of a container ("released"):
developbranch and use the most recent version.Additionally, we should be using GitHub Actions (GHA) to manage the build and publishing of containers to the OHDSI DockerHub. GHA should be used to manage both the "latest" and "released" builds.
Somewhat related (and if not we can spin up a new issue): the "ohdsi/braodsea-hades" container should be replaced by an "ohdsi/hades" container that is defined by a GHA in https://github.com/OHDSI/Hades.
Tagging @leeevans to try and make sure I've summarized our discussion. Also tagging @alondhe, @konstjar, @ablack3