11 Commits
Author SHA1 Message Date
tu 035550e183 feat(bump)!: nur Tag, kein Versions-Commit (#4)
ci/woodpecker/tag/plugins Pipeline was successful
## Was

Das Plugin `bump` setzt nur noch den Tag auf den auslösenden Commit. Es gibt keinen Versions-Commit mehr, `package.json` bleibt unberührt. Der Build nimmt die Version aus dem Tag (`CI_COMMIT_TAG`, im Beispiel als Build-Arg `VERSION`).

Grund: Mit Versions-Commit war der Head eines PRs immer der Bump-Commit mit `[skip ci]`. Dafür startet Woodpecker keine Pipeline, der verlangte Status-Check fehlt, der PR ist nicht mergebar (oumta-app). Ohne Commit bleibt der Head der des Entwicklers. Nebeneffekt: keine `update version`-Commits mehr in der Historie.

- `release_branch`: nächste stabile Version ist der höchste vorhandene Patch der Linie plus eins (vorher Patch-Bump aus `package.json`).
- Ein Commit, der schon ein `v*`-Tag trägt, wird nicht erneut getaggt. Ein Neustart der Pipeline baut also nicht doppelt.
- Image auf `alpine:3.20` wie `deploy`, Node wird nicht mehr gebraucht.
- `author_name` und `author_email` entfallen.

Breaking: Apps, die die Version aus `package.json` anzeigen, müssen sie aus dem Build-Arg lesen (Anforderung in oumta-deploy folgt). Release als `bump-v2.0.0`.

## Getestet

Lokal gegen ein Bare-Repo: feature von develop und von release, erste und weitere Betas, erneuter Lauf auf demselben Commit, hotfix mit und ohne Patch, production, `release_branch` mit vorhandenen stabilen Tags, Linie nach stabilem Tag, weitergelaufener Branch, fehlendes Token. Keine Commits auf den Branches.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
Reviewed-on: #4
2026-10-31 09:35:59 +00:00
tu 40d7997eca fix(bump): Release-Modell nach D8/D9, atomarer Push (#3)
ci/woodpecker/push/plugins Pipeline was successful
ci/woodpecker/tag/plugins Pipeline was successful
## Was

Folge-PR zum Review von #2 gegen `zugaenge.md`, D8, D9 und W4 in oumta-deploy.

- `production/*`: kein Bump, der Schritt bricht mit Hinweis ab. Ein Release ist ein Retag (D9, W4).
- `main` hat keine Release-Rolle mehr. Stabile Tags gibt es nur über `settings.release_branch` als Patch-Bump, für Repos ohne Majors wie oumta-keyklo. Die Commit-Message wird nicht mehr ausgewertet.
- Linie für dev-Tags: der nächste `release/*`- oder `hotfix/*`-Branch nach jüngster Merge-Base, bei Gleichstand die niedrigere Linie. Vorher zählten nur `release/*` und nur Branch-Spitzen.
- Existiert das stabile Tag einer Linie (`v2.4.0`), geht es mit dem nächsten Patch weiter (`v2.4.1-beta.0`). Vorher blieb die Beta-Linie auf `.0` stehen und der nächste Promote wäre an „Version noch frei“ gescheitert.
- `hotfix/X.Y` ohne Patch wird abgelehnt, es würde mit `release/X.Y` kollidieren.
- Branch und Tag gehen in einem atomaren Push. Vorher konnte der Bump-Commit ohne Tag landen und jeder weitere Lauf stieg mit Exit 0 aus.
- README: Regeln, Einschränkung des Secrets auf Images und Events, Paket-Schreibrecht von `oumta-ci` in `actions`, Beispiel ohne `develop`.

## Getestet

Lokal als Image gegen ein Bare-Repo: feature von develop, erste und zweite Beta, feature von release, hotfix mit und ohne Patch, production, `release_branch`, `release_line`, Linie nach stabilem Tag, weitergelaufener Branch, fehlendes Token.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #3
2026-10-30 18:06:42 +00:00
tu bcbfd8ed92 feat: Woodpecker-Plugin bump (#2)
ci/woodpecker/push/plugins Pipeline was successful
## Was

- `woodpecker/bump/`: Plugin, das aus Branch und Commit den nächsten Tag ableitet und setzt (dev, beta, hotfix→beta, main mit und ohne Marker, `release_line`), siehe D8 in oumta-deploy.
- `.woodpecker/plugins.yaml` baut jetzt beide Plugins mit Pfadfilter je Plugin; Release über Tag `bump-vX.Y.Z` bzw. `deploy-vX.Y.Z`.
- Nachträge zum deploy-Plugin aus #1: `plugin-docker-buildx:6` exakt wie in `WOODPECKER_PLUGINS_PRIVILEGED` (war nach dem Merge noch `6.1.2`), Registry-Login mit `oumta-ci` und Secret `oumta_ci_token` statt der globalen Secrets, README-Beispiele entsprechend (zugaenge.md in oumta-deploy).

## Voraussetzungen vor dem Tag

- Secret `oumta_ci_token` in Woodpecker für `actions/ci-cd`, freigegeben für `woodpeckerci/plugin-docker-buildx:6`, Events `push`, `tag`, `manual`.
- `oumta-ci` mit Paket-Schreibrecht in der Org `actions`.

## Getestet

Lokal gegen ein Bare-Repo: dev, beta, hotfix→beta, main mit und ohne Marker, `release_line`, weitergelaufener Branch, fehlendes Token.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #2
2026-10-30 16:44:50 +00:00
tu d071358196 feat: Woodpecker-Plugin deploy für oumta-deploy (#1)
## Was

Woodpecker-Plugin `deploy` (`git.uesome.de/actions/ci-cd/deploy`): schreibt ein gepushtes dev- oder beta-Image mit Digest nach `tanztee/oumta-deploy`. Die Umgebung entscheidet dort `ci/deploy-image.sh` anhand des Tags (`-dev.` → dev, `-beta.` → beta, sonst nichts; prod nur per PR). Digest per `crane`, kein Docker-Daemon nötig (dafür tanztee/oumta-deploy#20).

- `woodpecker/deploy/`: Dockerfile (`alpine:3.20`, bash, git, crane) und `deploy.sh`
- `.woodpecker/plugins.yaml`: Push/PR mit Änderungen unter `woodpecker/deploy/**` → nur Probe-Build (`dry_run`, ohne Secrets); Tag `deploy-vX.Y.Z` → Push als `:vX.Y.Z`
- `README.md`: Abschnitt „Woodpecker plugins“ mit Settings und Beispiel

Das Token von `oumta-ci` steht nur im Credential-Helper, nicht in URL oder Config.

## Getestet (lokal, crane als Stub, gegen Kopie von oumta-deploy `a74c73d`)

| Fall | Ergebnis |
| --- | --- |
| `v2.0.1-dev.…`, `AUTH_IMAGE` | `deploy(dev): oumta-auth …` |
| `v2.0.9-beta.7`, `APP_V{major}_IMAGE` | `APP_V2_IMAGE` in beta |
| `v2.0.1` | nichts zu tun, Exit 0 |
| keyklo, `envs: dev beta` | zwei Commits |
| gleicher Tag erneut | „bereits aktuell“ |
| ohne `deploy_token` | Abbruch mit Meldung |

Offen: echter Lauf gegen Registry und Gitea per HTTPS.

## Vor dem ersten Lauf in Woodpecker

1. `actions/ci-cd` aktivieren.
2. Repo-Secrets `registry_username`/`registry_password` (Schreibrecht auf Pakete der Org `actions`), nur Event `tag`, nur Image `woodpeckerci/plugin-docker-buildx`.
3. Prüfen, ob `plugin-docker-buildx:6.1.2` privilegiert laufen darf (`WOODPECKER_PLUGINS_PRIVILEGED`).

Tag `deploy-v1.0.0` erst nach dem Merge und grünem Probe-Build.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: #1
2026-10-30 14:23:43 +00:00
tu 662db558bd das ist krank und ich kann es nicht validieren 2026-03-18 22:20:02 +01:00
tu c5cd0f0430 fallback to version in package json 2026-03-14 18:15:33 +01:00
tu 69fe519f7a fix version bump strategy 2026-03-14 17:56:08 +01:00
tu 6f1913a542 add build paramenter 2026-03-09 19:09:20 +01:00
tu cb84cb354d remove early exit 2026-03-01 00:35:54 +01:00
tu 43d4a2b35e rc heißt jetzt beta sonst ändert sich nix 2026-03-01 00:17:04 +01:00
tu 03513bb1e4 add checkout-ref paramter 2026-02-28 23:35:05 +01:00
9 changed files with 600 additions and 36 deletions

No files matched your search

@@ -12,6 +12,10 @@ inputs:
description: Override image tag (defaults to standard tags) description: Override image tag (defaults to standard tags)
required: false required: false
default: "" default: ""
checkout_ref:
description: Git ref to checkout before build (e.g. refs/tags/v1.2.3)
required: false
default: ""
dockerfile: dockerfile:
description: Path to Dockerfile description: Path to Dockerfile
required: false required: false
@@ -42,6 +46,7 @@ runs:
with: with:
fetch-depth: 0 fetch-depth: 0
fetch-tags: true fetch-tags: true
ref: ${{ inputs.checkout_ref != '' && inputs.checkout_ref || '' }}
- name: Set up Docker Buildx - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3 uses: docker/setup-buildx-action@v3
@@ -12,6 +12,10 @@ inputs:
description: Override image tag (defaults to standard tags) description: Override image tag (defaults to standard tags)
required: false required: false
default: "" default: ""
checkout_ref:
description: Git ref to checkout before build (e.g. refs/tags/v1.2.3)
required: false
default: ""
dockerfile: dockerfile:
description: Path to Dockerfile description: Path to Dockerfile
required: false required: false
@@ -24,6 +28,10 @@ inputs:
description: Push image after build description: Push image after build
required: false required: false
default: "true" default: "true"
additional_build_args:
description: Additional Docker build args as newline-separated KEY=VALUE pairs
required: false
default: ""
registry_username: registry_username:
description: Registry username description: Registry username
required: true required: true
@@ -38,6 +46,7 @@ runs:
with: with:
fetch-depth: 0 fetch-depth: 0
fetch-tags: true fetch-tags: true
ref: ${{ inputs.checkout_ref != '' && inputs.checkout_ref || '' }}
- name: Set up Docker Buildx - name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3 uses: docker/setup-buildx-action@v3
@@ -108,3 +117,4 @@ runs:
VITE_KEYCLOAK_CLIENT_ID=${{ env.VITE_KEYCLOAK_CLIENT_ID != '' && env.VITE_KEYCLOAK_CLIENT_ID || vars.VITE_KEYCLOAK_CLIENT_ID }} VITE_KEYCLOAK_CLIENT_ID=${{ env.VITE_KEYCLOAK_CLIENT_ID != '' && env.VITE_KEYCLOAK_CLIENT_ID || vars.VITE_KEYCLOAK_CLIENT_ID }}
VITE_BASE_PATH=${{ env.VITE_BASE_PATH != '' && env.VITE_BASE_PATH || vars.VITE_BASE_PATH }} VITE_BASE_PATH=${{ env.VITE_BASE_PATH != '' && env.VITE_BASE_PATH || vars.VITE_BASE_PATH }}
VITE_ADMIN_API_BASE=${{ env.VITE_ADMIN_API_BASE != '' && env.VITE_ADMIN_API_BASE || vars.VITE_ADMIN_API_BASE }} VITE_ADMIN_API_BASE=${{ env.VITE_ADMIN_API_BASE != '' && env.VITE_ADMIN_API_BASE || vars.VITE_ADMIN_API_BASE }}
${{ inputs.additional_build_args }}
+176 -36
View File
@@ -5,6 +5,10 @@ inputs:
description: Node.js version to use description: Node.js version to use
required: false required: false
default: "24" default: "24"
release_line:
description: Release line for dev builds (e.g. 2.4 or 2.4.1) when it cannot be derived from the branch or PR target
required: false
default: ""
gitea_token: gitea_token:
description: Token for checkout/push (optional) description: Token for checkout/push (optional)
required: false required: false
@@ -34,25 +38,167 @@ runs:
with: with:
node-version: ${{ inputs.node_version }} node-version: ${{ inputs.node_version }}
- name: Bump patch version and tag - name: Bump version and tag
id: bump id: bump
shell: bash shell: bash
env:
INPUT_RELEASE_LINE: ${{ inputs.release_line }}
run: | run: |
EXISTING_TAG="$(git tag --points-at HEAD "v*" | head -n 1)" set -euo pipefail
if [ -n "${EXISTING_TAG}" ]; then
echo "Tag ${EXISTING_TAG} already points at this commit; skipping bump." REF="${GITHUB_HEAD_REF:-${GITEA_HEAD_REF:-${GITHUB_REF:-${GITEA_REF:-}}}}"
echo "tag=${EXISTING_TAG}" >> "${GITHUB_OUTPUT}" BASE_REF="${GITHUB_BASE_REF:-${GITEA_BASE_REF:-}}"
exit 0 BRANCH="${REF#refs/heads/}"
BASE_BRANCH="${BASE_REF#refs/heads/}"
if [[ -z "${BRANCH}" ]]; then
echo "Unable to determine branch from workflow context." >&2
exit 1
fi fi
REF="${GITHUB_REF:-${GITEA_REF}}"
BRANCH="${REF#refs/heads/}"
git fetch origin "${BRANCH}" --tags git fetch origin "${BRANCH}" --tags
git checkout "${BRANCH}" git checkout "${BRANCH}"
git pull --ff-only origin "${BRANCH}" git pull --ff-only origin "${BRANCH}"
BRANCH_SAFE="$(echo "${BRANCH}" | tr '/[:space:].' '-' | tr -cd '[:alnum:]_-')"
BRANCH_SAFE="$(echo "${BRANCH_SAFE}" | sed 's/^-*//;s/-*$//')" set_version() {
BRANCH_SAFE="${BRANCH_SAFE:-unknown}" npm version "$1" --no-git-tag-version --allow-same-version >/dev/null
}
read_package_version() {
node -p "require('./package.json').version"
}
normalize_release_base() {
local value="$1"
if [[ "${value}" =~ ^v?([0-9]+)\.([0-9]+)$ ]]; then
echo "${BASH_REMATCH[1]}.${BASH_REMATCH[2]}.0"
return 0
fi
if [[ "${value}" =~ ^v?([0-9]+)\.([0-9]+)\.([0-9]+)$ ]]; then
echo "${BASH_REMATCH[1]}.${BASH_REMATCH[2]}.${BASH_REMATCH[3]}"
return 0
fi
return 1
}
extract_release_base() {
local ref_name="$1"
local normalized
if [[ "${ref_name}" =~ ^release/(.+)$ ]]; then
if normalized="$(normalize_release_base "${BASH_REMATCH[1]}")"; then
echo "${normalized}"
return 0
fi
fi
return 1
}
infer_release_base_from_ancestor_release_branch() {
local best_release_base=""
local best_commit_time=0
local remote_ref
local release_branch
local release_base
local commit_time
# Best effort: not every repository has release branches.
git fetch --no-tags origin "+refs/heads/release/*:refs/remotes/origin/release/*" >/dev/null 2>&1 || true
while IFS= read -r remote_ref; do
release_branch="${remote_ref#origin/}"
if ! release_base="$(extract_release_base "${release_branch}")"; then
continue
fi
if ! git merge-base --is-ancestor "$(git rev-parse "${remote_ref}")" HEAD; then
continue
fi
commit_time="$(git show -s --format=%ct "${remote_ref}")"
if [[ "${commit_time}" -gt "${best_commit_time}" ]]; then
best_commit_time="${commit_time}"
best_release_base="${release_base}"
fi
done < <(git for-each-ref --format='%(refname:short)' refs/remotes/origin/release/*)
if [[ -n "${best_release_base}" ]]; then
echo "${best_release_base}"
return 0
fi
return 1
}
resolve_release_base() {
local package_version
local normalized
local inferred_release_base
if [[ -n "${INPUT_RELEASE_LINE}" ]]; then
if ! normalized="$(normalize_release_base "${INPUT_RELEASE_LINE}")"; then
echo "Invalid release_line input '${INPUT_RELEASE_LINE}'. Expected format: <major>.<minor> or <major>.<minor>.<patch>" >&2
exit 1
fi
echo "${normalized}"
return 0
fi
if extract_release_base "${BRANCH}" >/dev/null; then
extract_release_base "${BRANCH}"
return 0
fi
if [[ -n "${BASE_BRANCH}" ]] && extract_release_base "${BASE_BRANCH}" >/dev/null; then
extract_release_base "${BASE_BRANCH}"
return 0
fi
if inferred_release_base="$(infer_release_base_from_ancestor_release_branch)"; then
echo "${inferred_release_base}"
return 0
fi
package_version="$(read_package_version)"
if [[ "${package_version}" =~ ^([0-9]+)\.([0-9]+)\.[0-9]+([-.].*)?$ ]]; then
echo "${BASH_REMATCH[1]}.${BASH_REMATCH[2]}.0"
return 0
fi
echo "Unable to determine release base for branch '${BRANCH}'. Use release/<major>.<minor>[.<patch>], provide inputs.release_line, or ensure package.json contains a semantic version." >&2
exit 1
}
next_beta_version() {
local release_base="$1"
local escaped_base
local highest_beta
escaped_base="$(printf '%s' "${release_base}" | sed 's/\./\\./g')"
highest_beta="$(
git tag --list "v${release_base}-beta.*" \
| sed -nE "s/^v${escaped_base}-beta\.([0-9]+)$/\\1/p" \
| sort -n \
| tail -n 1
)"
if [[ -z "${highest_beta}" ]]; then
echo "${release_base}-beta.0"
else
echo "${release_base}-beta.$((highest_beta + 1))"
fi
}
next_dev_version() {
local release_base="$1"
local timestamp
while true; do
timestamp="$(date -u +%Y%m%d%H%M%S)"
if ! git rev-parse -q --verify "refs/tags/v${release_base}-dev.${timestamp}" >/dev/null; then
echo "${release_base}-dev.${timestamp}"
return 0
fi
sleep 1
done
}
case "${BRANCH}" in case "${BRANCH}" in
main) main)
COMMIT_MSG="$(git log -1 --pretty=%B)" COMMIT_MSG="$(git log -1 --pretty=%B)"
@@ -66,42 +212,36 @@ runs:
fi fi
if [[ -n "${TARGET_VERSION}" ]]; then if [[ -n "${TARGET_VERSION}" ]]; then
npm version "${TARGET_VERSION}" --no-git-tag-version --allow-same-version set_version "${TARGET_VERSION}"
BUMP_CMD="npm version patch --no-git-tag-version"
else else
npm version patch --no-git-tag-version npm version patch --no-git-tag-version >/dev/null
BUMP_CMD="npm version patch --no-git-tag-version"
fi fi
;; ;;
develop) release/*)
npm version prerelease --preid=dev --no-git-tag-version RELEASE_BASE="$(resolve_release_base)"
BUMP_CMD="npm version prerelease --preid=dev --no-git-tag-version" set_version "$(next_beta_version "${RELEASE_BASE}")"
;;
release*)
RELEASE_VERSION=""
if [[ "${BRANCH}" =~ ^release/v?([0-9]+\.[0-9]+\.[0-9]+)$ ]]; then
RELEASE_VERSION="${BASH_REMATCH[1]}"
fi
if [[ -n "${RELEASE_VERSION}" ]]; then
npm version "${RELEASE_VERSION}-rc.0" --no-git-tag-version --allow-same-version
BUMP_CMD="npm version prerelease --preid=rc --no-git-tag-version"
else
npm version prerelease --preid=rc-${BRANCH_SAFE} --no-git-tag-version
BUMP_CMD="npm version prerelease --preid=rc-${BRANCH_SAFE} --no-git-tag-version"
fi
;; ;;
*) *)
npm version prerelease --preid=nightly-${BRANCH_SAFE} --no-git-tag-version RELEASE_BASE="$(resolve_release_base)"
BUMP_CMD="npm version prerelease --preid=nightly-${BRANCH_SAFE} --no-git-tag-version" set_version "$(next_dev_version "${RELEASE_BASE}")"
;; ;;
esac esac
VERSION="$(node -p "require('./package.json').version")" VERSION="$(node -p "require('./package.json').version")"
while git rev-parse -q --verify "refs/tags/v${VERSION}" >/dev/null; do while git rev-parse -q --verify "refs/tags/v${VERSION}" >/dev/null; do
echo "Tag v${VERSION} already exists; trying next version." echo "Tag v${VERSION} already exists; trying next version."
${BUMP_CMD} case "${BRANCH}" in
VERSION="$(node -p "require('./package.json').version")" main)
npm version patch --no-git-tag-version >/dev/null
;;
release/*)
set_version "$(next_beta_version "${RELEASE_BASE}")"
;;
*)
set_version "$(next_dev_version "${RELEASE_BASE}")"
;;
esac
VERSION="$(read_package_version)"
done done
if git diff --quiet; then if git diff --quiet; then
+60
View File
@@ -0,0 +1,60 @@
# Builds the plugins in woodpecker/<name>/. A tag <name>-vX.Y.Z pushes
# git.uesome.de/actions/ci-cd/<name>:vX.Y.Z; pushes and PRs only test the build.
when:
- event: [push, pull_request]
path: 'woodpecker/**'
- event: tag
ref: [refs/tags/deploy-v*, refs/tags/bump-v*]
steps:
- name: deploy-plugin-check
image: woodpeckerci/plugin-docker-buildx:6
settings:
repo: git.uesome.de/actions/ci-cd/deploy
context: woodpecker/deploy
dockerfile: woodpecker/deploy/Dockerfile
dry_run: true
when:
event: [push, pull_request]
path: 'woodpecker/deploy/**'
- name: deploy-plugin
image: woodpeckerci/plugin-docker-buildx:6
settings:
registry: git.uesome.de
repo: git.uesome.de/actions/ci-cd/deploy
context: woodpecker/deploy
dockerfile: woodpecker/deploy/Dockerfile
tags: ${CI_COMMIT_TAG##deploy-}
username: oumta-ci
password:
from_secret: oumta_ci_token
when:
event: tag
ref: refs/tags/deploy-v*
- name: bump-plugin-check
image: woodpeckerci/plugin-docker-buildx:6
settings:
repo: git.uesome.de/actions/ci-cd/bump
context: woodpecker/bump
dockerfile: woodpecker/bump/Dockerfile
dry_run: true
when:
event: [push, pull_request]
path: 'woodpecker/bump/**'
- name: bump-plugin
image: woodpeckerci/plugin-docker-buildx:6
settings:
registry: git.uesome.de
repo: git.uesome.de/actions/ci-cd/bump
context: woodpecker/bump
dockerfile: woodpecker/bump/Dockerfile
tags: ${CI_COMMIT_TAG##bump-}
username: oumta-ci
password:
from_secret: oumta_ci_token
when:
event: tag
ref: refs/tags/bump-v*
+146
View File
@@ -4,6 +4,47 @@ This repo provides reusable Gitea Actions as composite actions that can be refer
### Bump Version ### Bump Version
Creates or updates the version in `package.json`, commits it, creates a matching Git tag, and pushes both.
Inputs:
- `node_version`: Node.js version to use. Default: `24`
- `release_line`: optional release line for dev builds. Format: `<major>.<minor>` or `<major>.<minor>.<patch>`. Overrides branch, PR target, inferred ancestor release branch, and `package.json`.
- `gitea_token`: optional token used for checkout and push
Branch and tag rules:
- `main`: creates release tags from the latest commit message (`release/x.y.z`, `release/x.y`, `hotfix/x.y.z`) or falls back to a patch bump.
- `release/<major>.<minor>` or `release/<major>.<minor>.<patch>`: creates the next beta tag for that release base, e.g. `v2.4.0-beta.3` or `v2.4.1-beta.3`.
- all other branches: create a dev tag for the resolved release base using a UTC timestamp, e.g. `v2.4.0-dev.20260314153045`.
Dev release line resolution order:
- `inputs.release_line`
- current branch if it matches `release/<major>.<minor>` or `release/<major>.<minor>.<patch>`
- PR target branch if it matches `release/<major>.<minor>` or `release/<major>.<minor>.<patch>`
- newest ancestor branch from `origin/release/*` (for feature branches created from release branches outside PR context)
- `major.minor` from `package.json`
If no release line can be resolved for a dev build, the action fails intentionally.
Examples:
Commit message examples on `main`:
- `release/2.4.0` -> `v2.4.0`
- `release/2.4` -> `v2.4.0`
- `hotfix/2.4.1` -> `v2.4.1`
Branch examples:
- `release/2.4` -> next `v2.4.0-beta.N`
- `release/v2.4.1` -> next `v2.4.1-beta.N`
- feature branch in a PR to `release/2.4` -> `v2.4.0-dev.<UTC_TIMESTAMP>`
- feature branch created from `release/v2.4.1` (without PR base) -> `v2.4.1-dev.<UTC_TIMESTAMP>` when the release branch tip is an ancestor
- feature branch outside a PR with `package.json` version `2.4.0` -> `v2.4.0-dev.<UTC_TIMESTAMP>`
- feature branch outside a PR with `release_line: 2.4` -> `v2.4.0-dev.<UTC_TIMESTAMP>`
Example: Example:
```yaml ```yaml
@@ -18,6 +59,21 @@ jobs:
gitea_token: ${{ secrets.GITEA_TOKEN }} gitea_token: ${{ secrets.GITEA_TOKEN }}
``` ```
Feature branch outside a PR:
```yaml
jobs:
bump-version:
runs-on: ubuntu-latest
permissions:
contents: write
steps:
- uses: tanztee/ci-cd/.github/actions/bump-version@main
with:
gitea_token: ${{ secrets.GITEA_TOKEN }}
release_line: 2.4
```
### Build and Push Docker Image ### Build and Push Docker Image
Example: Example:
@@ -61,3 +117,93 @@ jobs:
kubeconfig: ${{ secrets.KUBECONFIG }} kubeconfig: ${{ secrets.KUBECONFIG }}
registry: ${{ secrets.REGISTRY }} registry: ${{ secrets.REGISTRY }}
``` ```
## Woodpecker plugins
Plugins are Docker images built from `woodpecker/<name>/` by `.woodpecker/plugins.yaml`. A tag `<name>-vX.Y.Z` publishes `git.uesome.de/actions/ci-cd/<name>:vX.Y.Z`; pipelines pin that version. The push uses `oumta-ci` with the Woodpecker secret `oumta_ci_token`, so `oumta-ci` needs package write access in the org `actions`.
The secret `oumta_ci_token` holds the one token `oumta-ci` writes with. Limit it in Woodpecker to the images `woodpeckerci/plugin-docker-buildx:6`, `git.uesome.de/actions/ci-cd/bump` and `git.uesome.de/actions/ci-cd/deploy` and to the events `push`, `tag` and `manual` (zugaenge.md in oumta-deploy).
### deploy
Writes a pushed dev or beta image with its digest to `tanztee/oumta-deploy` (D16 there). `ci/deploy-image.sh` in oumta-deploy decides the environment from the tag: `-dev.` goes to dev, `-beta.` to beta, anything else is skipped (prod only via PR).
Settings:
- `var` (required): variable in `envs/<env>/images.env`, e.g. `AUTH_IMAGE`. `{major}` is replaced by the major of the tag (`APP_V{major}_IMAGE` -> `APP_V2_IMAGE`).
- `deploy_token` (required): token of `oumta-ci` (`oumta_ci_token`), write access to oumta-deploy
- `registry_username`, `registry_password`: read access to the registry for the digest (`oumta-ci` with the same token)
- `envs`: fixed environments instead of the tag rule, e.g. `dev beta` (oumta-keyklo)
- `tag`: default `CI_COMMIT_TAG`
- `registry`: default `git.uesome.de`
- `image`: default `<registry>/<CI_REPO>`
- `deploy_user`: default `oumta-ci`
- `deploy_repo`: default `https://git.uesome.de/tanztee/oumta-deploy.git`
Example:
```yaml
when:
event: tag
ref: refs/tags/v*
steps:
- name: build
image: woodpeckerci/plugin-docker-buildx:6
settings:
registry: git.uesome.de
repo: git.uesome.de/tanztee/oumta-auth
tags: ${CI_COMMIT_TAG}
build_args:
VERSION: ${CI_COMMIT_TAG##v}
username: oumta-ci
password:
from_secret: oumta_ci_token
- name: deploy
image: git.uesome.de/actions/ci-cd/deploy:v1.0.0
settings:
var: AUTH_IMAGE
registry_username: oumta-ci
registry_password:
from_secret: oumta_ci_token
deploy_token:
from_secret: oumta_ci_token
```
### bump
Derives the next version for the pushed branch and pushes it as a tag on the triggering commit. There is no version commit: the build takes the version from the tag (`CI_COMMIT_TAG`, e.g. as build arg `VERSION: ${CI_COMMIT_TAG##v}`), `package.json` stays untouched. The tag event then starts the build.
- `release/X.Y[.Z]`, `hotfix/X.Y.Z`: next `vX.Y.Z-beta.N` of that line (D8). A hotfix needs a patch number.
- `production/*`: no bump, the step fails. A release is a retag of a beta image (D9).
- the branch in `release_branch` (repos without majors, e.g. oumta-keyklo `main`): next stable `vX.Y.Z`, the highest existing patch of the line plus one
- any other branch: `vX.Y.Z-dev.<UTC timestamp>`; the line comes from `release_line`, the branch name, the nearest `release/*` or `hotfix/*` branch (newest merge base), or `major.minor` from `package.json`
If the stable tag of a line exists (`v2.4.0` after the release), the next patch of that line is used (`v2.4.1-beta.0`, `v2.4.1-dev.…`).
Only the commit that triggered the pipeline is tagged; if the branch moved on, the step exits without a tag and the newer pipeline takes over. A commit that already carries a `v*` tag is not tagged again, so a re-run does not build twice.
Settings:
- `git_token` (required): token of `oumta-ci` (`oumta_ci_token`), write access to the repo
- `git_user`: default `oumta-ci`
- `release_branch`: optional, branch that gets stable tags instead of dev tags
- `release_line`: optional, `<major>.<minor>[.<patch>]`, overrides every other rule
- `remote`: default `CI_REPO_CLONE_URL`
Example:
```yaml
when:
- event: push
branch: ['feature/**', 'release/**', 'hotfix/**']
- event: manual
steps:
- name: bump
image: git.uesome.de/actions/ci-cd/bump:v2.0.0
settings:
git_token:
from_secret: oumta_ci_token
```
+5
View File
@@ -0,0 +1,5 @@
# Woodpecker plugin: derives the next version and pushes it as a tag
FROM alpine:3.20
RUN apk add --no-cache bash git ca-certificates
COPY bump.sh /usr/local/bin/bump.sh
ENTRYPOINT ["/usr/local/bin/bump.sh"]
+158
View File
@@ -0,0 +1,158 @@
#!/usr/bin/env bash
# Woodpecker plugin "bump": derives the next version for the pushed branch and
# pushes it as a tag on the triggering commit. No commit is made; the build
# takes the version from the tag (CI_COMMIT_TAG). The tag event then starts
# the build.
#
# release/X.Y[.Z], hotfix/X.Y.Z next vX.Y.Z-beta.N (D8)
# production/* nothing: releases are retags (D9)
# settings.release_branch next free vX.Y.Z (repos without majors)
# any other branch vX.Y.Z-dev.<UTC timestamp>
set -euo pipefail
die() { echo "bump: $*" >&2; exit 1; }
BRANCH=${CI_COMMIT_BRANCH:?CI_COMMIT_BRANCH is missing (push event only)}
SHA=${CI_COMMIT_SHA:?CI_COMMIT_SHA is missing}
REMOTE=${PLUGIN_REMOTE:-${CI_REPO_CLONE_URL:?CI_REPO_CLONE_URL is missing}}
GIT_USER=${PLUGIN_GIT_USER:-oumta-ci}
RELEASE_LINE=${PLUGIN_RELEASE_LINE:-}
RELEASE_BRANCH=${PLUGIN_RELEASE_BRANCH:-}
[[ -n ${PLUGIN_GIT_TOKEN:-} ]] || die "settings.git_token is missing"
case $BRANCH in
production/*) die "no bump on $BRANCH: a release is a retag of a beta image (D9)" ;;
esac
# Token only via credential helper, never in a URL or config, so no log shows it
export GIT_USER PLUGIN_GIT_TOKEN
git config --global --add safe.directory "$PWD"
git config credential.helper '!f() { echo "username=$GIT_USER"; echo "password=$PLUGIN_GIT_TOKEN"; }; f'
git remote set-url origin "$REMOTE"
# The Woodpecker clone is shallow and has no tags; the version rules need both.
if [[ $(git rev-parse --is-shallow-repository) == true ]]; then
git fetch --quiet --unshallow origin
fi
git fetch --quiet --tags --force origin "+refs/heads/*:refs/remotes/origin/*"
# Tag exactly the commit that triggered the pipeline. A newer push on the
# branch starts its own pipeline, so this one steps aside.
head=$(git rev-parse -q --verify "origin/$BRANCH") || die "$BRANCH no longer exists on origin"
if [[ $head != "$SHA" ]]; then
echo "bump: $BRANCH moved past ${SHA:0:8}, the newer pipeline bumps"
exit 0
fi
git checkout --quiet "$SHA"
# A re-run must not produce a second tag and a second build for the same commit.
if existing=$(git tag --points-at HEAD 'v*' | head -n 1) && [[ -n $existing ]]; then
echo "bump: ${SHA:0:8} already carries $existing, nothing to do"
exit 0
fi
tag_exists() { git rev-parse -q --verify "refs/tags/v$1" >/dev/null; }
# "2.4" or "v2.4.1" -> "2.4.0" / "2.4.1"; fails for anything else
parse_line() {
[[ $1 =~ ^v?([0-9]+)\.([0-9]+)(\.([0-9]+))?$ ]] || return 1
echo "${BASH_REMATCH[1]}.${BASH_REMATCH[2]}.${BASH_REMATCH[4]:-0}"
}
# release/2.4 -> 2.4.0, hotfix/2.4.1 -> 2.4.1; a hotfix without a patch fails
line_of_branch() {
local kind name
[[ $1 =~ ^(release|hotfix)/(.+)$ ]] || return 1
kind=${BASH_REMATCH[1]} name=${BASH_REMATCH[2]}
[[ $kind == hotfix && ! $name =~ ^v?[0-9]+\.[0-9]+\.[0-9]+$ ]] && return 1
parse_line "$name"
}
# The release or hotfix branch whose merge base with HEAD is the newest, i.e.
# the line this commit was branched from most recently. On a tie (a hotfix
# forked from the same commit as the release) the lower line wins.
line_of_nearest_branch() {
local ref line base
while read -r ref; do
line=$(line_of_branch "${ref#origin/}") || continue
base=$(git merge-base "$ref" HEAD 2>/dev/null) || continue
echo "$(git show -s --format=%ct "$base") ${line//./ } $line"
done < <(git for-each-ref --format='%(refname:short)' refs/remotes/origin/release/ refs/remotes/origin/hotfix/) |
sort -k1,1nr -k2,2n -k3,3n -k4,4n | head -n 1 | { read -r _ _ _ _ line && echo "$line"; }
}
# major.minor.0 from the version in package.json, if there is one
line_of_package() {
local version
[[ -f package.json ]] || return 1
version=$(sed -nE 's/^[[:space:]]*"version"[[:space:]]*:[[:space:]]*"([^"]+)".*/\1/p' package.json | head -n 1)
version=$(parse_line "${version%%[-+]*}") || return 1
echo "${version%.*}.0"
}
# The line for this branch: setting, branch name, nearest release/hotfix
# branch, else major.minor of package.json.
resolve_line() {
if [[ -n $RELEASE_LINE ]]; then
parse_line "$RELEASE_LINE" || die "invalid settings.release_line '$RELEASE_LINE', expected <major>.<minor>[.<patch>]"
return
fi
line_of_branch "$BRANCH" && return
line_of_nearest_branch && return
line_of_package && return
die "no release line for '$BRANCH': use settings.release_line or a semantic version in package.json"
}
# The next stable version of a line: highest existing vX.Y.Z plus one patch.
next_stable() {
local line=$1 highest
highest=$(git tag --list "v${line%.*}.*" | sed -nE 's/^v[0-9]+\.[0-9]+\.([0-9]+)$/\1/p' | sort -n | tail -n 1)
echo "${line%.*}.$(( ${highest:--1} + 1 ))"
}
# A line whose stable tag exists was released; the next patch is the open one.
next_free_patch() {
local line=$1 patch
while tag_exists "$line"; do
patch=${line##*.}
line=${line%.*}.$((patch + 1))
done
echo "$line"
}
next_beta() {
local line=$1 highest
highest=$(git tag --list "v$line-beta.*" | sed -nE 's/^.*-beta\.([0-9]+)$/\1/p' | sort -n | tail -n 1)
echo "$line-beta.$(( ${highest:--1} + 1 ))"
}
next_dev() {
local line=$1 stamp
while :; do
stamp=$(date -u +%Y%m%d%H%M%S)
tag_exists "$line-dev.$stamp" || { echo "$line-dev.$stamp"; return; }
sleep 1
done
}
case $BRANCH in
release/* | hotfix/*)
line=$(line_of_branch "$BRANCH") || die "unusable branch name '$BRANCH', expected release/X.Y[.Z] or hotfix/X.Y.Z"
VERSION=$(next_beta "$(next_free_patch "$line")")
;;
*)
if [[ -n $RELEASE_BRANCH && $BRANCH == "$RELEASE_BRANCH" ]]; then
VERSION=$(next_stable "$(resolve_line)")
else
VERSION=$(next_dev "$(next_free_patch "$(resolve_line)")")
fi
;;
esac
TAG=v$VERSION
git tag "$TAG"
if ! git push --quiet origin "refs/tags/$TAG"; then
echo "bump: push of $TAG rejected, the newer pipeline bumps"
exit 0
fi
echo "bump: $TAG on $BRANCH (${SHA:0:8})"
+5
View File
@@ -0,0 +1,5 @@
# Woodpecker plugin: writes dev and beta image tags with digest to oumta-deploy
FROM alpine:3.20
RUN apk add --no-cache bash git ca-certificates crane
COPY deploy.sh /usr/local/bin/deploy.sh
ENTRYPOINT ["/usr/local/bin/deploy.sh"]
+35
View File
@@ -0,0 +1,35 @@
#!/usr/bin/env bash
# Woodpecker plugin "deploy": writes the pushed image with its digest to
# oumta-deploy. ci/deploy-image.sh there decides the environment from the tag
# (-dev. -> dev, -beta. -> beta, anything else -> nothing).
set -euo pipefail
die() { echo "deploy: $*" >&2; exit 1; }
VAR=${PLUGIN_VAR:?settings.var is missing}
REGISTRY=${PLUGIN_REGISTRY:-git.uesome.de}
IMAGE=${PLUGIN_IMAGE:-$REGISTRY/${CI_REPO:?CI_REPO is missing}}
TAG=${PLUGIN_TAG:-${CI_COMMIT_TAG:-}}
DEPLOY_USER=${PLUGIN_DEPLOY_USER:-oumta-ci}
DEPLOY_REPO=${PLUGIN_DEPLOY_REPO:-https://git.uesome.de/tanztee/oumta-deploy.git}
[[ -n $TAG ]] || die "no tag (settings.tag or tag event)"
[[ -n ${PLUGIN_DEPLOY_TOKEN:-} ]] || die "settings.deploy_token is missing"
major=${TAG#v}; major=${major%%.*}
VAR=${VAR//\{major\}/$major}
if [[ -n ${PLUGIN_REGISTRY_USERNAME:-} ]]; then
crane auth login "$REGISTRY" -u "$PLUGIN_REGISTRY_USERNAME" --password-stdin \
<<<"${PLUGIN_REGISTRY_PASSWORD:?settings.registry_password is missing}" >/dev/null
fi
# Token only via credential helper, never in a URL or config, so no log shows it
helper='!f() { echo "username=$DEPLOY_USER"; echo "password=$PLUGIN_DEPLOY_TOKEN"; }; f'
export DEPLOY_USER PLUGIN_DEPLOY_TOKEN
work=$(mktemp -d)
git -c credential.helper="$helper" clone --quiet "$DEPLOY_REPO" "$work/oumta-deploy"
git -C "$work/oumta-deploy" config credential.helper "$helper"
export DEPLOY_ENVS=${PLUGIN_ENVS:-}
export SOURCE_REPO=${CI_REPO:-} SOURCE_COMMIT=${CI_COMMIT_SHA:-}
"$work/oumta-deploy/ci/deploy-image.sh" "$VAR" "${IMAGE,,}:$TAG"