You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the OEC Dockerfile is missing a version label however, and the OEC github repo doesn't as-of-yet use release tagging.
Given this, it's proving difficult to make use of the Dockerfile because the build image can change at any time - something we can't have in production. The only real way for us to prevent this is spin up build infrastructure specificically for OEC, and the publish and manage the versioning ourselves.
It look like quite a number of docker images are published to your dockerhub accounts though 👍
On publish of an OEC release to master, it would probably make sense to build, tag, and push the docker image to dockerhub. This would allow for strategic version pinning, and eliminate the burden of OEC consumers having to manage their own infrastructure just to track, control and distribute OEC releases.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi there,
We're hoping to use the Docker image of OEC.
It looks like the OEC Dockerfile is missing a version label however, and the OEC github repo doesn't as-of-yet use release tagging.
Given this, it's proving difficult to make use of the Dockerfile because the build image can change at any time - something we can't have in production. The only real way for us to prevent this is spin up build infrastructure specificically for OEC, and the publish and manage the versioning ourselves.
It look like quite a number of docker images are published to your dockerhub accounts though 👍
https://hub.docker.com/u/opsgenie
https://hub.docker.com/u/atlassian
On publish of an OEC release to master, it would probably make sense to build, tag, and push the docker image to dockerhub. This would allow for strategic version pinning, and eliminate the burden of OEC consumers having to manage their own infrastructure just to track, control and distribute OEC releases.
Thanks!
The text was updated successfully, but these errors were encountered: