gitea/drone-docker
Archived
44
2
Fork 1
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Update README about new auto_tag logic #1

Merged
6543 merged 3 commits from lunny/update_readme into master 2022-06-26 22:35:53 +00:00
Conversation 0 Commits 3 Files Changed 1 +23 -1
1 changed files with 23 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.md
View File

@ -8,7 +8,29 @@
[![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):
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: <original_tag>
2) Tagging a pre-release version which ends with `-rcx`, `x` start from 1 to bigger number
It will produce the tags: <original_tag>
3) Tagging a latest stable release, we need to know if the version is the newest
It will produce the tags: <original_tag>, `1`,`1.1x`, `latest`
4) Tagging a low version stable release
It will produce the tags: <original_tag>, `1.1x`
## Build