Drone-plugins docker tag management issue

Drone Support
1

@tboerger && @bradrydzewski

I am appreciated if you can help for this issue.

I raised the problem with details in https://github.com/drone-plugins/drone-downstream/issues/32

Because of this issue, all builds with chained with downstream are broken.

I also hope if you fix the issue with 1.0.<build_number> for all other plugins as well, so we can avoid the problem in the future.

Updates

I have raised the PR (https://github.com/drone-plugins/drone-downstream/pull/33) to fix this issue

-    tags: [ latest, 1.0.0, 1.0, 1 ]
+    tags:
+      - latest
+      - 1.0
+      - 1
+      - 1.0.${DRONE_BUILD_NUMBER}

Please review and approve. If it is fine, please do the same for other drone-plugins.

By the way, can I apply the write permission in originzation drone-plugins?

2

Because of this issue, all builds with chained with downstream are broken.

Sorry, I am not sure I understand the issue. In general, we do not tag images per-build. Instead we have been moving toward a model where pushes / merges to master update the latest, and then git tags are used to create numbered docker tags.

3

ok, I understand better now and commented on the issue. The process I would like to put into place is described in my comment. I think we first should implement https://github.com/drone-plugins/drone-docker/issues/150