A new provider to push docker images(build artifact) to a Docker registry such as hub.docker.com.
Multiple images can be published to different registries with Docker Hub being the default registry.
Here is what I have in mind as options:
deploy:
docker:
- source: local-foo
target: foo/bar:edge
registry: hub.docker.com # default
user: foo
password:
- secure: ...
- source: local-foo:latest
target: bar/web:edge
registry: registry.heroku.com
user: foo
password:
- secure: ...
This should be easy to implement and in fact, I have already done so in JS. I have no experience with Ruby and cannot add it quickly myself.
Here is the script I use:
and the options (JSON) passed to it:
https://github.com/Zevere/WebAPI-Borzoo/blob/110ba3d81af3468678dd52abd815d9b79700d32d/.travis.yml#L41
Thanks for opening the issue. Could you review your proposed YAML configuration? It is an array of 10 elements, which I don't think is what you meant.
Thanks @BanzaiMan . I edited the proposed YAML configs.
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues
Please re-open: We're missing feedback from @BanzaiMan, but the issue isn't "solved already" nor is it "no longer applicable".
Any update on this, right now I could use something like below:
https://medium.com/vaidikkapoor/managing-open-source-docker-images-on-docker-hub-using-travis-7fd33bc96d65
Also would like an update on this.
A provider that at least provides a way of doing something like
docker login -p $PASSWORD -u $USERNAME && docker push $TAG in config would be helpful.
Here's a draft for a Docker provider based on the input on this ticket. I'm not sure it's capturing all the major use cases, and would love to get some feedback from you all:
I'm going to close this issue here. Let's continue the conversation on the PR. Feel free to re-open if needed though.