ipedrazas
quay.io repo doesn't seem to be updated
Sorry for asking, but is there an issue with CI/CD pipeline? https://quay.io/repository/ipedrazas/drone-helm doesn't seem to be updated for a while?
I also just noticed this. doesn't contain the latest merged PRs. I've been building my own image. Would appreciate an update to quay!
@nickychow I'm publishing images to https://hub.docker.com/r/peloton/drone-helm/ based on the fork at https://github.com/josmo/drone-helm
@ipedrazas let me know if you're still maintaining this and I'll totally PR all my changes back to you (I'll even volunteer the ci server I use to publish images) :)
When I moved the builds to gcp I decided to stop pushing images to quay. I’m not sure people should be using my images for their ci.
I understand that it´s a bit more of work, but from the security point of view is better if you control what runs in your environment.
@ipedrazas I'm using drone. #69 has a generic drone file that anyone can enable a fork and publish their own plugin
@ipedrazas I think it would be better to keep the quay image up to date, it is what all the documentation is pointed at and one of the explicit features of Drone is that plugins are just as easy as using a docker image for that pipeline run.
I have a use case for --set-string and that doesn't seem to be in the latest quay image. I'm building my own right now, but it sure would be nice to get the image updated.
If the image isn't up to date, this needs to be clarified in the documentation and/or in the Drone plugin registry. Especially since the Drone plugin documentation points to said image.
