Skip to content

feat: send branch_name in gerrit job requests#8

Open
RiSKeD wants to merge 1 commit into
mainfrom
feat/branch-based-job-requests
Open

feat: send branch_name in gerrit job requests#8
RiSKeD wants to merge 1 commit into
mainfrom
feat/branch-based-job-requests

Conversation

@RiSKeD

@RiSKeD RiSKeD commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

FirmwareCI workflows are branch-scoped. Add a top-level branch_name to the POST /v0/job body, taken from a new FWCI_BRANCH env var, so the server resolves the workflow on the intended branch instead of the project default. Set FWCI_BRANCH alongside FWCI_WORKFLOW_NAME in the CI job (it may differ from the Gerrit change's branch). Unset = server uses the default branch. Only affects workflow_name resolution; ignored for workflow_id.

@RiSKeD RiSKeD force-pushed the feat/branch-based-job-requests branch from a75ffb5 to 8fbed6a Compare June 16, 2026 14:22
FirmwareCI workflows are branch-scoped. Add a top-level branch_name to the
POST /v0/job body, taken from a new FWCI_BRANCH env var, so the server
resolves the workflow on the intended branch instead of the project default.
Set FWCI_BRANCH alongside FWCI_WORKFLOW_NAME in the CI job (it may differ
from the Gerrit change's branch). Unset = server uses the default branch.
Only affects workflow_name resolution; ignored for workflow_id.

Signed-off-by: Fabian Wienand <fabian.wienand@blindspot.software>
@RiSKeD RiSKeD force-pushed the feat/branch-based-job-requests branch from 8fbed6a to eee4250 Compare June 16, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant