Drone uses a .drone.yml file to determine what happens in response to a `git push` (or other events). I tend to use the build section (not shown below) for running tests, and the publish section for actually building and publishing the image from a Dockerfile. Here's a quick example of how the image creation and publishing works:
publish: docker: registry: quay.io username: $$QUAY_USERNAME password: $$QUAY_PASSWORD email: email@example.com repo: myorg/myrepo tag: $$TAG file: Dockerfile when: event: tag
Let's break this down a bit. The first registry field is optional if you are pushing to Docker Hub, but required if you want to push to anything else. It's sort of like how you have to explicitly specify the registry to pull from in `docker pull` for non-Docker Hub images.
The values for username and password correspond to a robot account on Quay.io we're using for publishing this particular image. Robots serve as an easily-restricted way to provide access to a repo without handing over the keys to the kingdom. You'll notice that we've got some weird $$QUAY_* values in there as well. These are variables that are substituted in via Drone's Secret Variables feature (don't commit un-encrypted credentials!).
The email value is ignored on Quay.io robot accounts, so I made something up. This will vary by image registry, so read your docs!
Repo points at the repo in Quay.io (excluding the quay.io prefix).
Similar to the Secret Variables feature we used above for username/password, $$TAG gets substituted with whatever tag was pushed during the build trigger. There are a few variables like this that you can inject.
The file key/val determines which Dockerfile is used to build the image before pushing.
And finally, then when clause. In our particular case, I only wanted to run this Docker image publish when a tag was pushed to git (signifying a new release). Not shown above are some previous sections that run our unit and integration tests. Those are set to run on every push. The end result is that all pushes (commits and tags alike) result in tests being ran, while only tags trigger our automated publish->deploy flow.
Hopefully this helps someone out there. Be sure to comment if you have questions.