-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drone/docker: Use a more standard format #7480
Conversation
Based on the plugin drone structure itself : https://github.com/drone-plugins/drone-docker/blob/ebce953fc443371d79b5a019fcc9c1976f60a09a/.drone.yml#L9 Use autotag : http://plugins.drone.io/drone-plugins/drone-docker/#autotag
This change will change the branch release with this the tag 1 and 1.9 will not be updated at each commit but at each tag but it will add consistency and simplicity by following what is "standard" for drone docker plugin. |
Codecov Report
@@ Coverage Diff @@
## master #7480 +/- ##
==========================================
+ Coverage 41.2% 41.21% +<.01%
==========================================
Files 469 469
Lines 63556 63533 -23
==========================================
- Hits 26190 26183 -7
+ Misses 33947 33933 -14
+ Partials 3419 3417 -2
Continue to review full report at Codecov.
|
What will happen if we tag 1.8.4? It will probably override :1 even if it was already for 1.9.0 release already, no? |
@lafriks yes but when version 1.9.0 that will update is only when rc end. This will maybe need to order for this release but for next the process would be :
It will be more logic to update 1 tag after end of rc period. |
@lafriks if we release a minor version for a past release (ex 1.8.4) then usually we will also release for the current one two. We do this in case of security patches where we tag past and release, then tag and release current. It is rare where we will release a patch for a previous version and not release for current. |
Moving to this standard that Drone uses will also allow us to copy their manifests so we can easily build docker images for ARM too. |
@techknowlogick That the next goal by just adding the suffix by platform and a step for pushing manifest. But since this PR as this is already modifying a little how we release I wanted to make it in two step to ease the review process. |
👌 For next PR here is some info that may help: I have a rough version of multi-arch manifets here: https://github.com/go-gitea/test-openldap We have ARM drone agent that we can use (it is only arm64, because I can't get docker to run in both 32-bit and 64-bit at same time). |
@techknowlogick I planned to use the same as drone plugin that seems to be a little advanced by managing tag but it is very similar. |
@sapk please backport to 1.9 :) |
* drone/docker: Use a more standard format Based on the plugin drone structure itself : https://github.com/drone-plugins/drone-docker/blob/ebce953fc443371d79b5a019fcc9c1976f60a09a/.drone.yml#L9 Use autotag : http://plugins.drone.io/drone-plugins/drone-docker/#autotag * use latest plugins/docker:linux-amd64 * remove useless cache_from * Don't depends on translations step
* don't make release-version deps on transalations since translations is only triggered by push on master (#7496) * drone/docker: Use a more standard format (#7480) * drone/docker: Use a more standard format Based on the plugin drone structure itself : https://github.com/drone-plugins/drone-docker/blob/ebce953fc443371d79b5a019fcc9c1976f60a09a/.drone.yml#L9 Use autotag : http://plugins.drone.io/drone-plugins/drone-docker/#autotag * use latest plugins/docker:linux-amd64 * remove useless cache_from * Don't depends on translations step
* drone/docker: Use a more standard format Based on the plugin drone structure itself : https://github.com/drone-plugins/drone-docker/blob/ebce953fc443371d79b5a019fcc9c1976f60a09a/.drone.yml#L9 Use autotag : http://plugins.drone.io/drone-plugins/drone-docker/#autotag * use latest plugins/docker:linux-amd64 * remove useless cache_from * Don't depends on translations step
Based on the plugin drone structure itself : https://github.com/drone-plugins/drone-docker/blob/ebce953fc443371d79b5a019fcc9c1976f60a09a/.drone.yml#L9
Use autotag : http://plugins.drone.io/drone-plugins/drone-docker/#autotag
Should fix #7476
Based on auto-tag, we should still have near similar tagging :
Previously, (before the drone update the broke it) we had :