0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2025-02-08 04:26:39 -05:00

chore(cleanup): forgejo.octopuce moved to invisible

This commit is contained in:
Earl Warren 2025-01-22 12:17:07 +01:00 committed by Earl Warren
parent 54c1bbd3e5
commit eed9fec135
2 changed files with 4 additions and 14 deletions

View file

@ -6,8 +6,7 @@ scheme = ["https", "http"]
skip_missing = false
include_verbatim = false
exclude = [
'https://forgejo\.octopuce\.forgejo\.org',
'http://private.forgejo.org',
'https://invisible.forgejo.org/forgejo/runner',
'https://code.forgejo.org/api/v1',
'https://codeberg.org/forgejo/forgejo/vX.Y/forgejo',
'https://dash\.cloudflare\.com/\?to\=/\:account/turnstile',

View file

@ -76,22 +76,13 @@ and the branches from https://codeberg.org/forgejo/forgejo.
The release is built on https://code.forgejo.org/forgejo-integration/runner, which is a mirror of https://code.forgejo.org/forgejo/runner.
The release is published on
https://forgejo.octopuce.forgejo.org/forgejo/runner, which is a mirror
of https://code.forgejo.org/forgejo-integration/runner. It has no public IP
and its role is to copy and sign release artifacts.
The release is published by
https://invisible.forgejo.org/forgejo/runner, which is a mirror
of https://code.forgejo.org/forgejo-integration/runner. Its role is to copy and sign release artifacts.
- Binaries are downloaded from https://code.forgejo.org/forgejo-integration/runner, signed and copied to https://code.forgejo.org/forgejo/runner.
- Container images are copied from https://code.forgejo.org/forgejo-integration to https://code.forgejo.org/forgejo
If publishing the release needs debug, it can be done manually:
- https://forgejo.octopuce.forgejo.org/forgejo-release/runner-debug has the same secrets as https://forgejo.octopuce.forgejo.org/forgejo-release/runner
- Make the changes, commit them, tag the commit with vX.Y.Z and force push the tag to https://forgejo.octopuce.forgejo.org/forgejo-release/runner-debug. Note that it does not matter that the tag is not on a commit that matches the release because this action only cares about the tag: it does not build any content itself, it copies it from one organization to another. However it matters that it matches a SHA that is found in the destination repository of the release otherwise it won't be able to set the tag (setting a tag on a non-existing sha does not work).
- Watch the action run at https://forgejo.octopuce.forgejo.org/forgejo-release/runner-debug/actions
- To skip one of the publish phases (binaries or container images), delete it and commit in the repository before pushing the tag
- Reflect the changes in a PR at https://code.forgejo.org/forgejo/runner to make sure they are not lost
It can also be done from the CLI with `forgejo-runner exec` and
providing the secrets from the command line.