forgejo/.forgejo/workflows
Earl Warren abf72a42e7
ci(release): upgrade v*.next.forgejo.org when the release is ready
The https://v$major.next.forgejo.org instances are polling for new
releases with a cron job every hour. This is not only a waste of
resources because there is nothing most of the time, it also imposes a
delay of maximum one hour when there is a new release.

When the release is published, notify the corresponding instance that
an upgrade is ready. In the request will 404 but leave a trace in the
logs which can trigger an upgrade script if wakeup-on-logs is
configured accordingly.

  GET https://v$major.next.forgejo.org/.well-known/wakeup-on-logs/forgejo-v$major

* v8 - a daemon watching on the web server logs was installed for
  https://v8.next.forgejo.org and will perform the upgrade.
* v7 - nothing will happen for https://v7.next.forgejo.org because
  it still relies on the hourly cron job.
* v1.21 - nothing will happen because https://v1.next.forgejo.org does
  not exist.

See also:

* https://forgejo.org/docs/next/developer/infrastructure
* https://code.forgejo.org/infrastructure/wakeup-on-logs
2024-07-01 12:52:59 +02:00
..
backport.yml [CI] configure backport to comment on the PR on failure 2024-04-15 18:23:57 +02: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 17:16:53 +02: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 Revert "[CI] pin go v1.22.2 version" 2024-04-05 05:31:00 +02:00
mirror.yml [CI] mirror to forgejo-integration daily instead of each commit 2024-02-17 11:55:52 +01:00
publish-release.yml ci(release): upgrade v*.next.forgejo.org when the release is ready 2024-07-01 12:52:59 +02:00
renovate.yml Update renovate to v37.421.2 2024-07-01 00:01:26 +00:00
testing.yml test(js): make test-frontend-coverage displays vitest coverage 2024-06-24 10:03:42 +02:00