-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create new container image automatically upon new release #4
Comments
If you make it automatic, could you please also publish the image to ghcr.io? |
Sure, I will take this up |
I did not have a chance to take this up. I have added this to my TODO list. |
Is it still manual, I don't see the latest release when I try to grab "latest"? |
Hi @Taomyn, the current version of DoH server is I assume you are trying to pull the doh-server container image from Docker Hub, expecting that there was an update to the images yesterday. Please correct me if I’m mistaken. The container image version remains the same and is up to date. When you pull the latest version of Yesterday, during a routine check, I observed that although the container images for version 2.3.6 were created, the release itself was missing. I have just created the releases from the tags in this GitHub repository. How are the images built when a new release is made?The image release process is still manual. I have alerts set up for new releases from the doh-server repository, and I promptly create new images on the same night. I test these images in my data center for a couple of days before rebuilding them for production and pushing them to Docker Hub. I need to find some time to automate it. For the automation, I want to ensure that the images are thoroughly tested to the same standard I currently use before marking them as the latest version. |
@satishweb thanks for the explanation and it all makes sense now. I just have the GitHub alert enabled for releases which is why I was checking. |
Container image creation is manual right now, it should be automatic
The text was updated successfully, but these errors were encountered: