Mirrors/woodpecker
1
0
Fork 0
mirror of https://github.com/woodpecker-ci/woodpecker.git synced 2026-03-15 17:13:46 +01:00
Code Issues Packages Projects Releases Wiki Activity

Tag pipeline with source information (#4796)

Browse Source 
Co-authored-by: oauth <woodpecker-bot@obermui.de>
Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>
Co-authored-by: Robert Kaussow <xoxys@rknet.org>
This commit is contained in:
Jener Rasmussen
2025-03-22 13:45:44 +01:00
committed by GitHub
parent 5ab0e46c21
commit 8d94071e2f
19 changed files with 208 additions and 653 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
docs/docs/20-usage/20-workflow-syntax.md
View File

@@ -594,20 +594,34 @@ For more details check the [matrix build docs](./30-matrix-workflows.md).
## `labels`
You can set labels for your workflow to select an agent to execute the workflow on. An agent will pick up and run a workflow when **every** label assigned to it matches the agents labels.
Use labels to select the agent that executes your workflow. An agent will execute a workflow only if **all** its assigned labels match the workflow's labels. For Kubernetes agents, these labels propagate to any related resources created during pipeline execution, including pods and secrets.
To configure additional agent labels, see the [agent configuration options](../30-administration/10-configuration/30-agent.md#agent_labels). Agents have pre-configured filters for the following labels:
To set additional agent labels, check the [agent configuration options](../30-administration/10-configuration/30-agent.md#agent_labels). Agents will have at least four default labels: `platform=agent-os/agent-arch`, `hostname=my-agent`, `backend=docker` (type of the agent backend) and `repo=*`. Agents can use a `*` as a wildcard for a label. For example `repo=*` will match every repo.
| Label | Description | Woodpecker managed |
|------------------------------------|--------------------------------------------------------------------|--------------------|
| `woodpecker-ci.org/forge-id` | Internal Forge identifier | 🤖 yes |
| `woodpecker-ci.org/repo-forge-id` | Repository identifier from the Forge | 🤖 yes |
| `woodpecker-ci.org/repo-id` | Internal repository identifier | 🤖 yes |
| `woodpecker-ci.org/repo-name` | Repository display name (excluding project/organization) | 🤖 yes |
| `woodpecker-ci.org/repo-full-name` | Repository display name (including project/organization) | 🤖 yes |
| `woodpecker-ci.org/branch` | Git branch name | 🤖 yes |
| `woodpecker-ci.org/org-id` | Internal organization/project identifier | 🤖 yes |
| `repo` | (deprecated) Combined repository and project name (`org/git_repo`) | 🤖 yes |
| `platform` | (deprecated) Agent OS and CPU architecture (e.g., `linux/amd64`) | 🧑‍💻 no |
| `hostname` | Agent name | 🧑‍💻 no |
| `backend` | Agent's backend technology (kubernetes, docker, local) | 🧑‍💻 no |
| `org-id` | Internal organization/project identifier | 🤖 yes |
Workflow labels with an empty value will be ignored.
By default, each workflow has at least the `repo=your-user/your-repo-name` label. If you have set the [platform attribute](#platform) for your workflow it will have a label like `platform=your-os/your-arch` as well.
You can add more labels as key-value pairs under the `labels` field in your pipeline. Labels marked as Woodpecker managed can not be set as part of the pipeline definition. Labels with empty values are ignored.
You can add additional labels as a key value map:
Specifying the [platform attribute](#platform) for your workflow automatically adds a corresponding `woodpecker-ci.org/platform` label, such as `woodpecker-ci.org/platform=your-os/your-arch`.
```diff
+labels:
+ location: europe # only agents with `location=europe` or `location=*` will be used
+ location: europe # Only agents with `location=europe` or `location=*` will execute this workflow.
+ weather: sun
+ hostname: "" # this label will be ignored as it is empty
+ hostname: "" # Ignored because the value is empty.
+ woodpecker-ci.org/forge-id: 1 # Ignored because it sets a managed label.
steps:
- name: build

12
docs/src/pages/migrations.md
View File

@@ -4,7 +4,17 @@ To enhance the usability of Woodpecker and meet evolving security standards, occ
## `next`
- No changes
- (Kubernetes) Deprecated `step` label on pod in favor of new namespaced label `woodpecker-ci.org/step`. The `step` label will be removed in a future update.
- Deprecated several labels in favor of equivalents with the `woodpecker-ci.org/` prefix. The deprecated labels will be removed in a future update.
The following labels are affected:
| Deprecated labels | New labels |
|-------------------|------------------------------------|
| `repo` | `woodpecker-ci.org/repo-full-name` |
| `platform` | `woodpecker-ci.org/platform` |
| `hostname` | `woodpecker-ci.org/hostname` |
| `backend` | `woodpecker-ci.org/backend` |
| `org-id` | `woodpecker-ci.org/org-id` |
## 3.0.0