From 7f0dacb7c6f72497c3a840333601f26cc160f074 Mon Sep 17 00:00:00 2001 From: Lunny Xiao Date: Wed, 22 Jun 2022 17:30:00 +0800 Subject: [PATCH 1/3] Update README about new auto_tag logic --- README.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3502803..fbac9bf 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,18 @@ [![Go Doc](https://godoc.org/github.com/drone-plugins/drone-docker?status.svg)](http://godoc.org/github.com/drone-plugins/drone-docker) [![Go Report](https://goreportcard.com/badge/github.com/drone-plugins/drone-docker)](https://goreportcard.com/report/github.com/drone-plugins/drone-docker) -Drone plugin uses Docker-in-Docker to build and publish Docker images to a container registry. For the usage information and a listing of the available options please take a look at [the docs](http://plugins.drone.io/drone-plugins/drone-docker/). +Drone plugin uses Docker-in-Docker to build and publish Docker images to a container registry. + +** This repository is a fork of drone-plugins/drone-docker with a auto_tag logic changed. + +When pushing a tag and using `auto_tag: true`, the logic is below(Not implemented yet): + +1) Tagging a pre-release version + It will produce the tags: +2) Tagging a latest stable release + It will produce the tags: , 1, latest +3) Tagging a low version stable release + It will produce the tags: ## Build -- 2.40.1 From 952f4c477cb906e5568dab4be92f5615d8a016ae Mon Sep 17 00:00:00 2001 From: Lunny Xiao Date: Sun, 26 Jun 2022 12:28:00 +0800 Subject: [PATCH 2/3] Update the rules of auto tag --- README.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index fbac9bf..f1ce64e 100644 --- a/README.md +++ b/README.md @@ -14,12 +14,14 @@ Drone plugin uses Docker-in-Docker to build and publish Docker images to a conta When pushing a tag and using `auto_tag: true`, the logic is below(Not implemented yet): -1) Tagging a pre-release version +1) Tagging a dev version which ends with `-dev` It will produce the tags: -2) Tagging a latest stable release - It will produce the tags: , 1, latest -3) Tagging a low version stable release - It will produce the tags: +2) Tagging a pre-release version which ends with `-rcx`, `x` start from 1 to bigger number + It will produce the tags: +3) Tagging a latest stable release, we need to know if the version is the newest + It will produce the tags: , 1, 1.1x, latest +4) Tagging a low version stable release + It will produce the tags: , 1.1x ## Build -- 2.40.1 From 855f494870f0e0454bc66c5064253aec325066f4 Mon Sep 17 00:00:00 2001 From: Lunny Xiao Date: Sun, 26 Jun 2022 12:35:22 +0800 Subject: [PATCH 3/3] Add branches auto tag --- README.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f1ce64e..6e6ff61 100644 --- a/README.md +++ b/README.md @@ -14,14 +14,23 @@ Drone plugin uses Docker-in-Docker to build and publish Docker images to a conta When pushing a tag and using `auto_tag: true`, the logic is below(Not implemented yet): +For git branches: + +1) Tagging `main`` branch + It will produce the tags: `dev`. +2) Tagging `release/vxxx` branch + It will produce the tags: `1.1x-dev` + +For git tags: + 1) Tagging a dev version which ends with `-dev` It will produce the tags: 2) Tagging a pre-release version which ends with `-rcx`, `x` start from 1 to bigger number It will produce the tags: 3) Tagging a latest stable release, we need to know if the version is the newest - It will produce the tags: , 1, 1.1x, latest + It will produce the tags: , `1`,`1.1x`, `latest` 4) Tagging a low version stable release - It will produce the tags: , 1.1x + It will produce the tags: , `1.1x` ## Build -- 2.40.1