Appearance
Git sources
Add a Git source to an infrastructure job to check out a repository before its steps run.
Prepare the repository
Under Administration → Services → Git → Repository roots, add the repository and its credentials. SSH access requires an SSH key and a known-hosts set.
Select a Monitoring Runner pool and set the check interval. Monitoring Runners need Git installed and access to the repository. The monitoring pool checks for changes independently of the pool used for checkout. It can use different Runners from the build pool.
An optional infrastructure webhook prompts immediate checks. Periodic checks also detect changes when no webhook is configured or a notification is missed.
Branch specifications and logical names
The repository's Branch specification controls which refs jobs can use. For branches and pull-request refs:
text
+:refs/heads/(*)
+:refs/(pull/*)Parentheses select the logical name: refs/heads/main becomes main, and refs/pull/42/head becomes pull/42/head. Use +: to include refs and -: to exclude them. A single * matches one or more characters, including /. More specific patterns take precedence; the last equally specific pattern wins.
Configure the job
In the job editor, enable Git source under Features. Select a repository or supply its ID through a variable, such as {{ vars.repository }}. The job's Default branch can override the repository default and also supports variables.
The job's Branch filter matches logical names from the repository specification. For example, +:pull/* limits the job to pull-request refs.
Use an infrastructure template to share the Git source configuration across jobs.
Choose where checkout runs
Set Checkout location to Build Runner to check out directly in the build workspace. The build Runner needs Git and repository access. This mode includes Git metadata and supports reusing a checkout.
Choose Checkout Runner pool when the build Runners cannot reach the repository. Select a pool whose Runners have Git and repository access. Ordyn prepares the selected commit in that pool and delivers its files to the build Runner through the pools' Cache nodes. Checkout and build Runners must use the same operating system; their processor architectures can differ. The build Runner needs access to its assigned Cache node and does not need Git for this checkout.
The Runner performing checkout needs OpenSSH for SSH repositories and Git LFS when Pull Git LFS objects is enabled. Submodules and LFS files are prepared in the checkout pool. Repository monitoring remains independent of this setting.
Checkout through a separate pool delivers a fresh set of files into an absent or empty Workspace destination, including . for the workspace root. It excludes .git metadata and history. Build steps that run commands such as git describe need checkout on the build Runner; steps that only need the revision can use {{ job.git.commit }}. Each run receives its own source snapshot, with the same commit retained during retries.
Select a branch for a manual run
Select a branch or pull-request ref when running the job, or leave it empty to use the default. Pull requests appear as Git refs, without hosting-service titles or open/closed status.
Build changed branches automatically
Add a Git changes automation to the job. Monitoring needs a repository that can be resolved from configured values without starting a run. Its first check establishes a baseline; subsequent new or changed matching refs start builds pinned to the detected commits. Re-enabling the automation or changing its repository or branch selection establishes a new baseline.
See Build Gitea pull requests to configure webhook notifications. Use a Webhook received automation when each delivery should directly start a run using webhook payload values.
Inspect the built source and changes
Open Prepare Git source in the run log to follow checkout progress and identify the repository, requested ref, selected commit, and destination. When using a checkout pool, the same task shows source preparation and delivery. Its completion summary includes the prepared ref and commit and the elapsed time, including waits and delivery.
The run header identifies the recorded branch or ref for Git builds. Open Changes to inspect its commit and changes since the last build of that ref. The first build uses an earlier default-branch build for comparison when available. These changes describe the build history, not a proposed pull-request merge.
Build scripts can use Git source variables, such as {{ job.git.commit }}, after checkout.