-
Notifications
You must be signed in to change notification settings - Fork 124
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
consider building and pushing Interop Runner Docker image in CI #1552
Comments
I am happy to contribute the required GitHub Action in case there is interest from the neqo maintainers. |
@mxinden that would be great. I had a cron job setup, but I can supply the necessary secrets to get something running if you want to do the initial work. I remember having a bunch of problems with the docker hub setup at the time, so it might be easier to use the GitHub image store (I've moved to that for other projects). |
I prepared #1554. Let me know what you think. |
Neqo's interop runner Docker image is now hosted on GitHub's container registry and continuously updated via a daily GitHub action. See mozilla/neqo#1552 for details.
Neqo's interop runner Docker image is now hosted on GitHub's container registry and continuously updated via a daily GitHub action. See mozilla/neqo#1552 for details.
I noticed that the neqo interop runner image is now 3 years (!) old: https://hub.docker.com/r/neqoquic/neqo-qns/tags. I assume that building / pushing was done manually using this script so far.
May I suggest to push a new interop runner on every push to master, or on a daily (?) cron job? GitHub Actions has some predefined workflows that should make building and pushing Docker images pretty straightforward. For inspiration, here is quic-go's workflow, and Quinn has one as well.
The text was updated successfully, but these errors were encountered: