forgejo/.forgejo/workflows
Earl Warren 305ec55b10
[v7.0/forgejo] chore(ci): notify the k8s cluster about experimental releases
This is in preparation of the migration of the v*.next.forgejo.org
instances currently managed at https://code.forgejo.org/infrastructure/k8s

The key difference is that the former system relies on ad-hoc scripts
and creates one k8s cluster for each instance, sharing nothing between
them.

The newer k8s cluster is used for all and requires significantly less
ad-hoc tooling.

See also:

* https://code.forgejo.org/infrastructure/next-digest
* https://code.forgejo.org/infrastructure/k8s-cluster/src/branch/main/k8s.md#updating-v-next-forgejo-org

(cherry picked from commit dab156b452)
2024-11-04 14:37:59 +01:00
..
backport.yml [CI] backport: show event information for debug purposes 2024-03-31 07:01:34 +00:00
build-release-integration.yml Disable duplicate builds 2024-03-25 13:24:53 +01:00
build-release.yml fix(release): add missing ARG RELEASE_VERSION 2024-04-17 16:06:43 +00:00
cascade-setup-end-to-end.yml [CI] simplify end-to-end test cascading PR 2024-03-20 18:16:56 +01:00
e2e.yml tests: run JavaScript tests when web_src/js is modified 2024-07-08 18:58:25 +00:00
mirror.yml [CI] mirror to forgejo-integration daily instead of each commit 2024-02-17 11:55:52 +01:00
publish-release.yml [v7.0/forgejo] chore(ci): notify the k8s cluster about experimental releases 2024-11-04 14:37:59 +01:00
renovate.yml Update ghcr.io/visualon/renovate Docker tag to v37.272.0 2024-03-27 07:32:23 +00:00
testing.yml Revert "[CI] pin go v1.22.2 version" 2024-04-05 04:40:24 +00:00