@lissyx Maybe you can better use the github webhooks instead of the scriptworker to link to github on the docker hub page. Also, the automatic builds of docker hub could speed up the pipeline.
@lissyx There is already an existing docker hub account by mozilla. It should be better to request access for that organization instead of creating a new one.
@lissyx Maybe you can better use the github webhooks instead of the scriptworker to link to github on the docker hub page. Also, the automatic builds of docker hub could speed up the pipeline.
There's a reason we use scriptWorker, maintaining two different CI / CD pipeline will be a burden.
* [x] Decouple training from building #3056 * [ ] Create docker hub account * [ ] Add scriptworker upload ability to docker hub
So the situation is complicated:
docker save command we issue does produce v1.0 docker image specOk, Docker Hub Automated builds can support hooks/, so we might be able to rely on that for push-to-tag on releases.
How it looks on my own repo:

Still waiting on the people who are supposed to be in charge of the mozilla org on Docker Hub.
So, #3157 merged, new alpha tagged:
latest on https://hub.docker.com/r/mozilla/deepspeech-train/tagsr0.8 branch PR merge still running on TaskCluster, but once it is merged it should produce docker image on Docker Hub
It should be good but there are issues on both Github and CircleCI, so nothing is starting for now, and I can't be sure it's all okay.
r0.8 branch PR merge still running on TaskCluster, but once it is merged it should produce docker image on Docker Hub
It should be good but there are issues on both Github and CircleCI, so nothing is starting for now, and I can't be sure it's all okay.
And it worked.