From 2221b2314441688596e2aa8d8ea5abf1a2e5819b Mon Sep 17 00:00:00 2001 From: 3wc <3wc@doesthisthing.work> Date: Wed, 17 Jan 2024 22:02:56 -0300 Subject: [PATCH 1/2] =?UTF-8?q?013=20=E2=86=92=20in=20progress?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/federation/resolutions/{drafts => in-progress}/013.md | 0 mkdocs.yml | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename docs/federation/resolutions/{drafts => in-progress}/013.md (100%) diff --git a/docs/federation/resolutions/drafts/013.md b/docs/federation/resolutions/in-progress/013.md similarity index 100% rename from docs/federation/resolutions/drafts/013.md rename to docs/federation/resolutions/in-progress/013.md diff --git a/mkdocs.yml b/mkdocs.yml index 1d2d58a..fa26c39 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -115,9 +115,9 @@ nav: - federation/resolutions/in-progress/index.md - federation/resolutions/in-progress/016.md - federation/resolutions/in-progress/017.md + - federation/resolutions/drafts/013.md - "Draft": - federation/resolutions/drafts/index.md - - federation/resolutions/drafts/013.md - "Finance": federation/finance.md - "Membership": federation/membership.md - "Minutes": From 01e65bef1bcf56f3b5c6f495534c26357ef5b746 Mon Sep 17 00:00:00 2001 From: 3wc <3wc@doesthisthing.work> Date: Mon, 5 Feb 2024 12:51:38 -0300 Subject: [PATCH 2/2] Explain auto recipe catalogue generation --- docs/maintainers/handbook.md | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/docs/maintainers/handbook.md b/docs/maintainers/handbook.md index 3116c5e..a2cfc50 100644 --- a/docs/maintainers/handbook.md +++ b/docs/maintainers/handbook.md @@ -427,6 +427,34 @@ You can pass `--publish` to have `abra` automatically publish those changes. In order to have `abra` publish changes for you automatically, you'll have to have write permissons to the git.coopcloud.tech repository and your account must have a working SSH key configuration. `abra` will use the SSH based URL connection details for Git by automagically creating an `origin-ssh` remote in the repository and pushing to it. +## How is I make the catalogue automatically regenerate after new versions are published? + +"I'd like to make it so that whenever I push a new git tag to the +[`coop-cloud/rallly` repository](https://git.coopcloud.tech/coop-cloud/rallly) +(probably [using `abra recipe +release`](#how-do-i-release-a-new-recipe-version)), it automatically does the +[recipe catalogue generation steps(#how-do-i-generate-the-recipe-catalogue)" + +1. Check whether tag builds are already trying to run: go to + https://build.coopcloud.tech, search for the recipe name (in this case taking + you to https://build.coopcloud.tech/coop-cloud/rallly/settings). If there are + failing builds, or if you see builds succeeding but catalogue regeneration + doesn't seem to be happening, then either dive in and try and fix it, or ask + for help in [`#coopcloud-tech`](https://matrix.to/#/#coopcloud-tech:autonomic.zone) +2. Otherwise, click "activate repository". You probably want to set the "disable pull + requests" and "disable forks" options; they won't work anyway, but the + failures might be confusing. +3. Make sure there is a `generate recipe catalogue` step in the recipe's + `.drone.yml` -- if there isn't, you can copy [the one from + `coop-cloud/rallly`](https://git.coopcloud.tech/coop-cloud/rallly/src/branch/main/.drone.yml#L24-L38) unchanged. +4. That's it! Now, when you push a new tag, the recipe catalogue will regenerate + automatically. You can test this by re-pushing a tag (e.g. `git push origin + :0.5.0+3.5.1 && git push 0.5.0+3.5.1`) + +## How does automatic catalogue regeneration work? + +TODO + ## How do I enable healthchecks A healthcheck is an important and often overlooked part of the recipe configuration. It is part of the configuration that the runtime uses to figure out if a container is really up-and-running. You can tweak what command to run, how often and how many times to try until you assume the container is not up.