yamllint Create "official" docker builds

It looks like there's only a latest tag on docker hub: https://hub.docker.com/r/sdesbure/yamllint/tags/

Perhaps add another job that builds all [git] tags that starts with v?

Jun 20 '18 21:06 jbergstroem

Hi Johan, this Docker repo is not affiliated with us. Maybe you should contact the author, @sdesbure?

Jun 21 '18 07:06 adrienverge

Hello, I'm the guy from the Docker repo. As my GitHub repo (https://github.com/sdesbure/docker_yamllint) is not the one from @adrienverge, I have no access to 'vXXX' stuff :( The only way to do it would be to merge the Dockerfile (and the hooks folder if possible) into this particular project. If @adrienverge is OK, I can do a PR!

Jun 25 '18 15:06 sdesbure

Overlooked that it was not the same author. Apologies. I would also be happy with helping out in merging a Dockerfile here.

Jun 25 '18 21:06 jbergstroem

Hi Sylvain, Johan,

I don't see the need to add a Dockerfile (or any other packaging conf file: .spec, .dsc, package.json, etc.) in this repo. It just runs pip install yamllint, right? Am I missing a hidden feature?

Jun 26 '18 07:06 adrienverge

Hi Adrien, One nice feature of Docker Hub is that you can build an image every time there's a change on the source code of the repo. So we could create a Dockerfile that build yamllint and create the image every time master is changed. We can also trigger a build every time a new tag starting with v for example is created and tag the image with the same name (v1.2.3 for example).

But this can only be done if the Dockerfile is in the same repository. If it's not, there's no way to do it except manually (and then you know that it won't last).

I'm not requesting this change but if you're interested I can make a PR

Jun 26 '18 12:06 sdesbure

@adrienverge I run this as part of a CI pipeline (thinking I might not be alone) Having to (re-)install yamllint as part of setting up the runner is something I'd like to avoid (I probably invoke it 300 times a day). I can obviously create my own dockerfile and maintain it (like @sdesbure did), but I think there's more users than us that would enjoy using yamllint as part of their own containerized landscape.

Jun 26 '18 16:06 jbergstroem

I created a repository that is always up-to-date within 24 hours with the latest release of this project. It is kind a special because I use six8/pyinstaller-alpine to create a minimal image containing only the executable and nothing else. I also had the need for this due to CI. @adrienverge I seriously hope that you rethink your position regarding this topic because listening to the GitHub release events in your TravisCI build would be much more efficient.

https://github.com/Fleshgrinder/docker-yamllint