Infrastructure/forgejo
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-25 08:54:17 -05:00
Code Issues Activity
forgejo/docker/manifest.tmpl

25 lines
956 B
Go HTML Template
Raw Normal View History

Unify nightly naming across binaries and docker images (#24116) Proposal found here: https://github.com/go-gitea/gitea/issues/23654 TODO: make non-breaking (can we publish docker image using dev and nightly prefix? at same time). if anyone has advice please comment :) If this PR is merged, then I can add redirects to the downloads site.
2023-04-24 10:43:19 -05:00
image: gitea/gitea:{{#if build.tag}}{{trimPrefix "v" build.tag}}{{else}}{{#if (hasPrefix "refs/heads/release/v" build.ref)}}{{trimPrefix "refs/heads/release/v" build.ref}}-{{/if}}nightly{{/if}}
drone/docker: prepare multi-arch release + provide arm64 image (#7571) * drone/docker: prepare multi-arch release * Add docker-linux-arm64 pipeline * add arm 64 build to manifest * tag dry-run + indent * Fix notify dependency
2019-07-24 12:21:12 -05:00
{{#if build.tags}}
Wrap unless-check in docker manifests (#23079) Should fix the following: > failed to render template: Evaluation error: Helper 'unless' called with wrong number of arguments, needed 2 but got 3 Signed-off-by: jolheiser <john.olheiser@gmail.com>
2023-02-22 17:33:31 -05:00
{{#unless (contains "-rc" build.tag)}}
Do not publish docker release images on `-dev` tags (#25471) Try to prevent what happened with tag `v1.21.0-dev` as outlined in #25193. Unfortunately, we cannot really test if it works as intended as we would need to release a new `dev` tag for that. Fixes #25193 (or at least attempts to). --------- Co-authored-by: jolheiser <john.olheiser@gmail.com>
2023-06-23 14:52:24 -05:00
{{#unless (contains "-dev" build.tag)}}
drone/docker: prepare multi-arch release + provide arm64 image (#7571) * drone/docker: prepare multi-arch release * Add docker-linux-arm64 pipeline * add arm 64 build to manifest * tag dry-run + indent * Fix notify dependency
2019-07-24 12:21:12 -05:00
tags:
{{#each build.tags}}
- {{this}}
{{/each}}
Change docker tag logic (#16421) * Change docker logic * Apply suggestions from code review Co-authored-by: Kyle D. <kdumontnu@gmail.com> * docs Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Lauris BH <lauris@nix.lv> Co-authored-by: Kyle D. <kdumontnu@gmail.com>
2021-07-14 12:08:43 -05:00
- "latest"
Adjust manifest to prevent tagging latest on rcs (#22811)
2023-02-19 09:24:08 -05:00
{{/unless}}
Do not publish docker release images on `-dev` tags (#25471) Try to prevent what happened with tag `v1.21.0-dev` as outlined in #25193. Unfortunately, we cannot really test if it works as intended as we would need to release a new `dev` tag for that. Fixes #25193 (or at least attempts to). --------- Co-authored-by: jolheiser <john.olheiser@gmail.com>
2023-06-23 14:52:24 -05:00
{{/unless}}
drone/docker: prepare multi-arch release + provide arm64 image (#7571) * drone/docker: prepare multi-arch release * Add docker-linux-arm64 pipeline * add arm 64 build to manifest * tag dry-run + indent * Fix notify dependency
2019-07-24 12:21:12 -05:00
{{/if}}
manifests:
-
Unify nightly naming across binaries and docker images (#24116) Proposal found here: https://github.com/go-gitea/gitea/issues/23654 TODO: make non-breaking (can we publish docker image using dev and nightly prefix? at same time). if anyone has advice please comment :) If this PR is merged, then I can add redirects to the downloads site.
2023-04-24 10:43:19 -05:00
image: gitea/gitea:{{#if build.tag}}{{trimPrefix "v" build.tag}}{{else}}{{#if (hasPrefix "refs/heads/release/v" build.ref)}}{{trimPrefix "refs/heads/release/v" build.ref}}-{{/if}}nightly{{/if}}-linux-amd64
drone/docker: prepare multi-arch release + provide arm64 image (#7571) * drone/docker: prepare multi-arch release * Add docker-linux-arm64 pipeline * add arm 64 build to manifest * tag dry-run + indent * Fix notify dependency
2019-07-24 12:21:12 -05:00
platform:
architecture: amd64
os: linux
-
Unify nightly naming across binaries and docker images (#24116) Proposal found here: https://github.com/go-gitea/gitea/issues/23654 TODO: make non-breaking (can we publish docker image using dev and nightly prefix? at same time). if anyone has advice please comment :) If this PR is merged, then I can add redirects to the downloads site.
2023-04-24 10:43:19 -05:00
image: gitea/gitea:{{#if build.tag}}{{trimPrefix "v" build.tag}}{{else}}{{#if (hasPrefix "refs/heads/release/v" build.ref)}}{{trimPrefix "refs/heads/release/v" build.ref}}-{{/if}}nightly{{/if}}-linux-arm64
drone/docker: prepare multi-arch release + provide arm64 image (#7571) * drone/docker: prepare multi-arch release * Add docker-linux-arm64 pipeline * add arm 64 build to manifest * tag dry-run + indent * Fix notify dependency
2019-07-24 12:21:12 -05:00
platform:
architecture: arm64
os: linux
Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch (#18551) * Make docker gitea/gitea:v1.16-dev etc refer to the latest build on that branch One of the problems with our current docker tagging is that although we have strict version tags, latest and dev we do not have a way for docker users to track the current release branch. This PR simply suggests that we use the 1.x-dev tag for these and we build and push these. This will give users who want or need unreleased bug fixes the option of tracking the pre-release version instead of simply jumping to dev. Signed-off-by: Andrew Thornton <art27@cantab.net> Co-authored-by: KN4CK3R <admin@oldschoolhack.me> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2022-02-03 03:47:27 -05:00
variant: v8
Reference in a new issue Copy permalink