CI/CD Pipelines & Helm: glossary
158 terms, in plain words, with where each one is taught.
- --force-replace (--force (Helm))
- Helm 4's flag (formerly --force) to delete and recreate objects that cannot be patched, with downtime. Lesson 40.26
- --history-max
- How many revisions
helm upgradekeeps (default 10). You can only roll back to a revision still stored. Lesson 40.19 - --reset-then-reuse-values (--reuse-values, --reset-values)
- helm upgrade flags for the previous values: reset uses only this command's, reuse keeps the old ones but ignores new chart defaults, reset-then-reuse takes new defaults plus the old values. Lesson 40.21
- --rollback-on-failure (--atomic, --cleanup-on-fail)
- On a failed upgrade, roll back to the last deployed revision automatically (implies --wait). --atomic is the old name. Good for shared environments, bad for debugging. Lesson 40.26
- --set-string (--set-json, --set-file, --set-literal)
- Variants of --set: force a string, give a JSON value, read a file's content, or take the text literally. Applied by kind, whatever order you type them. Lesson 40.21
- --show-only (-s (helm template))
helm template ... --show-only templates/X.yamlrenders just one template: the fastest way to see what a value does. Lesson 40.21- --wait (Helm) (--wait-for-jobs, --timeout (Helm))
- Makes helm wait until every resource is ready, within --timeout (default 5m). Without it Helm reports deployed as soon as the objects are sent. Lesson 40.26
- -f (Helm) (--values)
-f FILEpasses a values file to helm. Several are merged left to right, so the last one wins. Lesson 40.21- ##[error] (##[section])
- Markers the agent writes into a job log: ##[section] where each step starts and ends, ##[error] where something failed. Read upwards from the first ##[error]. Lesson 40.4
- ${{ if }} (${{ each }})
- Compile-time logic in a pipeline file: keep lines only if a condition holds, or repeat them for each item of a list. Sees only parameters and YAML variables. Lesson 40.9
- agent (pipeline)
- The program that executes a pipeline's jobs on some machine. GitLab and GitHub call it a runner. Lesson 40.4
- agent pool (pipeline) (pool:)
- A named group of agents.
pool: oncall-labmeans a run waits until one agent of that pool is free. Lesson 40.4 - agent workspace (Pipeline.Workspace, Build.SourcesDirectory, _work)
- The directory on the agent where a job's files live, under /home/azagent/myagent/_work/N. On a self-hosted agent it survives between runs. Lesson 40.4
- another operation is in progress (pending lock)
- The helm error when a revision is stuck in pending-*: a killed helm process left the lock. Roll back (or fix the record) instead of uninstalling. Lesson 40.26
- app repo (application repository)
- The git repo with the source code, tests, Dockerfile and CI pipeline file. Developers own it and change it all day. Lesson 40.1
- approval (approvals, ci approve)
- A check on an environment: a named person must click Approve before the stage may start. It lives on the environment, so editing the YAML cannot skip it. Lesson 40.11
- appVersion (.Chart.AppVersion)
- Chart.yaml metadata saying which app version the chart ships by default. The chart version is the package's own number; bump it on any chart change. Lesson 40.19
- azagent
- The Linux user the lab's pipeline agent runs as. It is not you: it has no kubeconfig, registry login or git credentials of its own. Lesson 40.1
- Azure Pipelines (Azure Pipeline)
- The pipeline part of Azure DevOps: it reads azure-pipelines.yml from the repo and runs its stages, jobs and steps on agents. Lesson 40.4
- azure-pipelines.yml
- The pipeline file in the app repo. Azure DevOps reads it from the commit being built, so a pipeline change is reviewed like code. Lesson 40.4
- AzureKeyVault@2
- The Azure Pipelines task that reads secrets from a Key Vault at run time, so they never live in Azure DevOps. Lesson 40.7
- base chart (platform base chart, java-service)
- A chart owned by the platform team that every service depends on, so probes, security settings and labels are the same everywhere. Lesson 40.29
- before_script (default:)
- GitLab: commands run before every job's script, often set once under default:. Lesson 40.14
- branch (branches, feature branch)
- A named line of commits in git. main is the shared one; a feature branch holds a change until it is merged. Lesson 40.2
- build once, deploy many
- The rule that one build makes one image, and that same image (same digest) runs in dev, test and prod. Only the configuration differs per environment. Rebuilding for prod gives bytes nobody tested: a newer base image, a newer dependency, a different compiler. Lesson 40.1
- Cache@2 (restoreKeys, pipeline cache)
- The task that saves a directory (like Maven's .m2/repository) at the end of a job and restores it in later runs, keyed on files like pom.xml. restoreKeys are fall-backs. Lesson 40.9
- chart repository (index.yaml, helm repo add, helm search repo)
- A web server with index.yaml listing every chart version and its .tgz.
helm repo add NAME URLremembers it;helm search repolists what it has. Lesson 40.29 - Chart.lock (helm dependency update, helm dependency build)
- The exact dependency versions a range resolved to.
helm dependency updatewrites it;helm dependency buildreproduces it (what CI runs). Lesson 40.29 - Chart.yaml (chart version, apiVersion: v2)
- The file naming a Helm chart: its name, its own version, the appVersion it ships, and its dependencies. Lesson 40.19
- charts.lab
- The lab's Helm chart repository, a web server of the platform team that hands out charts such as java-service. Lesson 40.1
- checksum/config (checksum annotation (Helm))
- A pod-template annotation holding a hash of the rendered ConfigMap, so any config change changes the pod template and rolls the pods. Lesson 40.24
- ci (simulator) (ci runs, ci watch, ci show)
- The lab command that stands in for the Azure DevOps and GitLab web UI: list runs, wait for one, show its tree of stages, read job logs, approve a stage. Lesson 40.1
- ci play
- The simulator command that starts a manual GitLab job, like its Play button in the GitLab UI.
- ci validate
- The simulator command that compiles a pipeline from git.lab and prints it with every template pasted in, like "Download full YAML" in the web UI. Lesson 40.9
- CI_ variables ($CI_COMMIT_SHA, $CI_DEFAULT_BRANCH, $CI_REGISTRY)
- GitLab's predefined variables, plain environment variables in every job: the commit, the default branch, the registry and image path, the pipeline id. Lesson 40.14
- ci-bot (platform-ci)
- The lab's machine accounts: ci-bot owns the git.lab token pipelines use; platform-ci is the name pipeline commits are signed with.
- CI/CD (CD)
- Continuous integration and continuous delivery (or deployment): build and test every change automatically (CI), then put the tested build into the environments (CD). Lesson 40.1
- computed values (merged values)
- The final values after merging every layer: what the templates actually see. Lesson 40.21
- config repo (configuration repository, payments-config)
- The git repo that says what runs where: the Helm chart and one values file per environment. A deploy is a commit to it. Lesson 40.1
- continuous delivery
- Every build that passes CI could go to production at the press of a button: prod is one approval away, but a human (or a change ticket) still says yes. Lesson 40.1
- continuous deployment
- Every build that passes CI goes to production automatically, with no human step. Banks rarely do this; they do continuous delivery. Lesson 40.1
- database migration (Flyway, Liquibase, schema migration)
- A script that changes a database's tables to what the new code expects. Flyway and Liquibase are the common Java tools; a rollback does not undo it. Lesson 40.26
- default (Helm)
- The template function
default X VALUE: VALUE if non-empty, else X. 0 and false count as empty. Lesson 40.24 - delivery (software delivery)
- The whole path from "code is merged" to "it runs for users": build, test, package, deploy to each environment. Lesson 40.1
- dependsOn
- The pipeline key that says which stages or jobs must finish before this one starts. By default a stage depends on the one before it. Lesson 40.4
- deployment job (deployment:, runOnce)
- A pipeline job that deploys to an environment (deployment: instead of job:). It records the deployment and waits for the environment's checks. Lesson 40.11
- displayName
- The label a step, job or stage shows in the run's log and tree, instead of the raw command. Lesson 40.4
- diverged (divergent branches)
- Your branch and the server's both have commits the other lacks. A plain
git pullthen refuses and asks whether to merge or rebase. Lesson 40.2 - drift (Helm) (drift check)
- The live objects no longer match what Helm deployed, because someone edited them by hand.
helm get manifest | kubectl diff -f -shows it. Lesson 40.19 - env: mapping (env:)
- The env: block of a pipeline step: environment variables for that one step, the only way a secret variable reaches a script. Lesson 40.7
- environment (Azure Pipelines) (payments-prod, payments-dev, ci env)
- A named deploy target the server tracks: its deployment history and the checks (approvals, locks) a stage must pass before deploying there. Lesson 40.11
- environment (delivery)
- One place the app runs: dev (developers try things), test (checks before release), prod (real users). Often one Kubernetes namespace or cluster each. Lesson 40.1
- exclusive lock
- An environment check that lets only one run deploy there at a time. Lesson 40.11
- executor (shell executor, Docker executor)
- How a GitLab runner runs jobs: shell runs them directly on the runner machine; Docker and Kubernetes executors run each job in an image. Lesson 40.14
- expand, deploy, contract (expand and contract, expand/contract)
- The safe order for schema changes: add new columns while keeping old ones, deploy the code that uses them, remove the old ones later. Keeps rollbacks possible. Lesson 40.26
- extends: (extends template)
- Says the whole pipeline IS a template (often from a platform team's repo); the service only fills in parameters, so required stages cannot be removed. Lesson 40.9
- fast-forward (non-fast-forward)
- A push that only adds commits on top of what the server has. Git accepts only these; "non-fast-forward" means your branch is behind or has split from the server's. Lesson 40.2
- feature flag (config) (feature switch)
- An on/off setting the app reads at start to enable a feature, so the same image can behave differently per environment. Lesson 40.1
- fetch first
- The rejected-push reason meaning the server has commits you have never downloaded. Fix:
git pull --rebase, then push again. Lesson 40.2 - field manager
- The name recorded as owner of a field under server-side apply, for example helm or kubectl. Lesson 40.19
- float64 (1.5e+06)
- A decimal-number type. Every number from a values file becomes one, and big ones print as 1.5e+06 unless piped through int. Lesson 40.21
- force push (git push --force, --force)
git push --force: tell the server "replace your branch with mine" even if it throws away commits it has. Refused on protected branches; never the fix for a rejected push. Lesson 40.2- git commit --amend (--amend)
- Replace the last commit with a new one (new message or content). Rewrites history, so only before pushing.
- git describe (git describe --tags)
- Names the current commit relative to the nearest tag: v1.5.0-3-g9c41e7a is 3 commits after v1.5.0, at commit 9c41e7a. Lesson 40.2
- git fetch
- Download new commits from the server without changing your branch.
git pullis fetch plus combining them with your work. Lesson 40.2 - git reset --hard (git reset, reset --hard)
- Move your branch back to another commit and throw away everything after it, including uncommitted changes. Fine on your own copy, wrong for shared history. Lesson 40.2
- git revert
- Make a new commit that does the opposite of an old one. History keeps both, so it is the safe undo on a shared branch. Lesson 40.2
- git switch (git switch -c)
git switch NAMEmoves you onto a branch;-ccreates it first. Lesson 40.2- git tag (annotated tag, lightweight tag, git tag -a)
- A fixed name on one commit, like v1.5.0. An annotated tag (
-a -m) also stores who, when and why. Tags are pushed only withgit push origin TAG. Lesson 40.2 - git.lab
- The lab's git server, like GitLab or GitHub: it stores the repos and refuses forbidden pushes such as a force push to main. Lesson 40.1
- GitLab CI (.gitlab-ci.yml, GitLab CI/CD)
- GitLab's built-in pipelines, defined in .gitlab-ci.yml. Every top-level key that is not a keyword is a job; stages are just names. Lesson 40.14
- global (values) (global:, .Values.global)
- The values section Helm copies into every subchart; otherwise a subchart cannot see its parent's values. Lesson 40.29
- glpat (glpat-)
- The prefix of a GitLab personal access token. Seeing glpat- in a file or log means a GitLab token has leaked.
- green run (red run, went red, goes green)
- Green: the pipeline run succeeded. Red: it failed. Named after the colours the web UI shows.
- Groovy
- A programming language for the Java VM, used to write Jenkins pipelines. Lesson 40.14
- helm diff (helm diff upgrade, helm-diff)
- A Helm plugin (add-on command) that prints what an upgrade would change, like git diff, without applying anything. Lesson 40.29
- Helm hook (helm.sh/hook, hook-weight, pre-upgrade hook)
- An object in a chart (usually a Job) that Helm runs at a set moment, such as before an upgrade, instead of applying it with the rest. Not part of the release. Lesson 40.26
- Helm release (releases (Helm), release name)
- One installed copy of a chart in a namespace, under a name, with a numbered list of revisions. Lesson 40.19
- helm rollback
- Adds a new revision whose content is an older one ("Rollback to 1"). Revision numbers never go backwards; history only grows. Lesson 40.19
- helm test (helm.sh/hook: test)
- Runs the chart's test pods against the installed release: smoke tests like calling the health endpoint. Lesson 40.26
- hook-delete-policy (before-hook-creation, hook-succeeded, hook-failed)
- When Helm deletes a hook object. before-hook-creation,hook-succeeded removes successful runs and keeps a failed one for its logs. Lesson 40.26
- imageID (containerStatuses imageID)
- The field in a pod's status with the digest the node actually pulled. The ground truth for "what is running", unlike the requested image: field. Lesson 40.11
- IndividualCI
- The Build.Reason of a run started by a push that matched the trigger. Manual and PullRequest are other reasons. Lesson 40.4
- int64
- A whole-number type.
--set replicaCount=3gives one, so it prints normally. Lesson 40.21 - Jenkins (Jenkinsfile)
- An older, self-hosted CI server. A Jenkinsfile describes the pipeline in Groovy: an agent label, stages, sh steps, credentials, an input gate. Lesson 40.14
- JSON Schema (values.schema.json)
- A standard way to describe which keys a JSON or YAML document may have and what type each is. A chart's values.schema.json makes Helm reject wrong values. Lesson 40.19
- kstatus
- A library that decides whether a Kubernetes object is ready (Deployment rolled out, PVC bound). Helm 4's --wait uses it. Lesson 40.19
- Kubernetes@1
- The Azure Pipelines task that, with command: login and a Kubernetes service connection, writes a temporary kubeconfig so later steps' kubectl and helm work. Lesson 40.7
- logging command (##vso, task.setvariable)
- A line like ##vso[task.setvariable variable=x]value that a script prints; the agent acts on it (sets a variable, marks an error) instead of just logging it. Lesson 40.7
- macro syntax ($(x), macro)
$(x): replaced in a step's text just before the step runs. An unknown name is left as literal $(x), which bash then runs as a command. Lesson 40.7- masking (***)
- The agent replacing a secret's exact value with *** in logs. A base64 or partial copy is not masked, so it is a safety net, not access control. Lesson 40.7
- matrix (strategy: matrix, maxParallel)
- Runs one job several times with different variables (build_jdk17, build_jdk21). maxParallel caps how many run at once. Lesson 40.9
- merge commit (merge commits)
- A commit with two parents that joins two lines of history. Useful for merging a branch; noise when made for every push race. Lesson 40.2
- merge request (merge requests, MR)
- GitLab's name for a proposal to merge a branch into main that others review and approve first. GitHub calls it a pull request. Lesson 40.1
- Mihai
- A (fictional) colleague on the payments team in the lab stories, who pushes to the same repos you do.
- multi-line script trap
- A multi-line script: step runs without set -e, so its result is only the last command's exit code: a failing test followed by an echo is green. Lesson 40.4
- mutable tag (moving tag, mutable tags)
- A tag that is moved to a new image on every build (latest, main, 1.5). Fine for finding the newest image, never for deploying. Lesson 40.11
- named template (Helm) (define, _helpers.tpl, include)
- A snippet defined once with define in _helpers.tpl and used with include, which returns it as text you can pipe. Names are global, so prefix them with the chart name. Lesson 40.24
- needs: (needs, DAG)
- GitLab: start this job as soon as the listed jobs finish, instead of waiting for the whole previous stage. The jobs form a DAG, arrows with no loops. Lesson 40.14
- Nexus (Sonatype Nexus, Artifactory)
- An artifact repository many banks run for Maven artifacts, npm packages and often Docker images. Artifactory is the other common one. Lesson 40.14
- nil pointer (nil pointer evaluating)
- The render error "tried to read a field of something that does not exist", like .Values.image.tag when image is missing. Lesson 40.24
- NOTES.txt (Helm) (NOTES)
- A chart file rendered and printed after install or upgrade, usually "how to reach the app". It is not applied to the cluster. Lesson 40.19
- OCI chart (oci://, helm push, helm package)
- A chart packaged (
helm package) and pushed to an OCI registry next to images, then used as oci://registry/path with --version. Lesson 40.29 - origin/main (origin/HEAD)
- Your local record of where main was on the server (origin) the last time you fetched or pushed. Lesson 40.2
- output variable (isOutput, isOutput=true, stageDependencies)
- A value a named step publishes (isOutput=true) so later jobs or stages can read it with $[ dependencies... ] or $[ stageDependencies... ]. Missing a piece gives an empty string. Lesson 40.7
- PagerDuty
- A paging service that alerts the on-call engineer's phone when monitoring detects a problem.
- pipeline artifact (publish:, download:)
- A bundle of files a job uploads (
publish) so later jobs of the same run can fetch it (download). The way files move between jobs. Lesson 40.4 - pipeline condition (condition:, succeeded(), always())
- An expression deciding whether a stage, job or step runs. The default is succeeded(); a custom one replaces it, so wrap it in and(succeeded(), ...). Lesson 40.4
- pipeline job (job:, jobs:)
- A unit of work that runs on one agent, with its own fresh workspace. Two jobs never share files except through artifacts. Lesson 40.4
- pipeline run (run (pipeline), runs)
- One execution of a pipeline, started by a push, a schedule or a person, with a number and a log. Lesson 40.4
- pipeline step (steps:, script step)
- One command inside a job: a script, a bash script, or a task. Steps of a job run in order in the same workspace. Lesson 40.4
- pipeline task (task:, Docker@2, Bash@3)
- A ready-made, versioned pipeline step with inputs instead of commands, like Docker@2 (build and push an image). The number is its major version. Lesson 40.4
- pipeline template (template:, steps template)
- A reusable YAML file of steps, jobs, stages or variables, with parameters, pasted into the pipeline when it compiles. Lesson 40.9
- pipeline trigger (trigger:, CI trigger)
- The part of the pipeline file that says which pushes start a run: branches to include or exclude, and paths. Lesson 40.4
- post-job step (Post-job)
- A step a task adds after your last step, for example Cache@2 saving the cache once the job succeeded. Lesson 40.9
- pre-receive hook
- A check the git server runs on every incoming push before accepting it. "pre-receive hook declined" means the check said no, for example a force push to a protected branch. Lesson 40.2
- predefined variable (predefined variables, Build.BuildId, Build.SourceVersion)
- A variable Azure Pipelines sets for every run: the run id, the commit, the branch, why it started. Read as $(Build.BuildId), or $BUILD_BUILDID in a script. Lesson 40.4
- protected branch (protected branches)
- A branch the git server guards: no force pushes, often no direct pushes at all, only reviewed merge requests. It makes main an honest history. Lesson 40.2
- protected variable (masked variable, file variable)
- GitLab CI/CD variable options: masked hides it in logs, protected exposes it only on protected branches and tags, file puts the value in a temp file and gives the path. Lesson 40.14
- rebase (git rebase, git pull --rebase, pull.rebase)
- Take your commits off, lay the server's commits down, then replay yours on top, as if you had started after them. History stays a straight line. Lesson 40.2
- release Secret (sh.helm.release.v1, owner=helm)
- Where Helm stores each revision: a Secret in the release's namespace holding the chart, values and rendered manifest, gzipped and base64-encoded. Lesson 40.19
- release status (deployed, superseded, pending-upgrade)
- The state of a Helm revision: deployed (current), superseded (older), failed, or pending-* while an operation runs (or after its process died). Lesson 40.19
- render (Helm) (rendered, helm template)
- Fill a chart's templates with values to get plain Kubernetes YAML.
helm templaterenders without touching the cluster. Lesson 40.19 - rendered manifest (helm get manifest)
- The final YAML Helm applied for a revision.
helm get manifest RELEASEprints it; comparing it with the live objects shows drift. Lesson 40.19 - report (game) (report)
- The simulator command
report TEXTthat hands in a finding for a mission objective, like writing it in the team channel. - required (Helm) (required)
- The template function that stops rendering with your message if a value is empty:
required "config.gatewayUrl is required" .Values.config.gatewayUrl. Lesson 40.24 - resources.repositories (@templates)
- Declares another git repo (for example shared templates) under a short alias; FILE@alias then means FILE from that repo, at the pinned ref. Lesson 40.9
- revision (Helm) (helm history)
- One numbered version of a Helm release. Every install, upgrade and rollback adds one;
helm historylists them. Lesson 40.19 - rules: (rules, when: manual)
- GitLab: a list of if: tests, checked when the pipeline is created, deciding whether a job exists at all. when: manual makes it wait for someone to press Play. Lesson 40.14
- runtime expression ($[ ])
$[ variables.x ]: worked out while the run is going, for values that only exist after an earlier job produced them. Lesson 40.7- secret variable (secret variables)
- A pipeline variable the server stores encrypted, hides as *** in logs, and does not give to scripts unless you map it with env:. Lesson 40.7
- selector labels (spec.selector, field is immutable)
- The labels a Deployment uses to find its pods. spec.selector can never change, so a chart that puts a version in it fails every upgrade. Lesson 40.24
- server-side apply (SSA)
- The API server itself merges a change and records which tool owns each field, so two tools changing one field get a conflict instead of a silent overwrite. Lesson 40.19
- SHA
- The hash used as a commit's ID (a3f9c12...). A short SHA is its first 7 characters, a common image tag. Lesson 40.2
- smoke test (smoke tests, smoke check)
- A quick check that the installed app basically works, run right after deploying. Lesson 40.26
- Sprig
- A big library of extra template functions (default, quote, b64enc, sha256sum...) that Helm adds to Go templates. Lesson 40.24
- subchart (subcharts, chart dependency, dependencies:)
- A chart included in another chart through the dependencies list of Chart.yaml. The parent passes it values under its name. Lesson 40.29
- System.AccessToken
- A secret token each run gets, allowing it to call Azure DevOps (for example to push to a repo) as the pipeline itself. Lesson 40.4
- template action ({{ }})
- Anything between {{ and }} in a Helm template; Helm replaces it with the result. Everything else is copied as is. Lesson 40.24
- template expression (${{ }}, compile time)
${{ variables.x }}: filled in while Azure DevOps compiles the pipeline file, before any agent starts. It can shape the pipeline. Lesson 40.7- template parameter (parameters:, parameters.)
- An input a pipeline template declares, with a type, a default and allowed values; the caller fills it in like a function argument. Lesson 40.9
- template pipeline (| (template))
A | fin a template passes A into function f as its last argument:.Values.tag | default "1.0". Lesson 40.24- text/template (Go template (Helm))
- Go's template library, the language Helm templates are written in. Lesson 40.24
- the dot (Helm) ($ (Helm), scope (template))
- The object
.refers to in a template: the root at the top, the current item inside with and range.$always means the root. Lesson 40.24 - toYaml | nindent (nindent, toYaml, indent)
- toYaml turns a map into YAML text; nindent N adds a newline and indents every line by N, so the block lands at the right column. Lesson 40.24
- tpl (Helm) (tpl)
- The function that renders a value as a template, so a value can contain {{ .Release.Namespace }}. Lesson 40.24
- transitive dependency (transitive dependencies)
- A library your library needs. A rebuild can pick up a newer one without anyone changing your code. Lesson 40.11
- trunk-based development (trunk)
- Everyone merges small changes into main (the "trunk") often; branches live hours or days, not months, so main is always close to deployable. Lesson 40.2
- umbrella chart
- A chart whose only job is to include other charts as subcharts. Lesson 40.29
- upstream branch (git push -u, tracking branch)
- The server branch your local branch is linked to, set once with
git push -u origin NAME, so plaingit pushandgit pullknow where to go. Lesson 40.2 - user-supplied values (helm get values)
- Only the values you passed (-f, --set), without chart defaults.
helm get valuesprints them;--allprints the full merge. Lesson 40.21 - values file (values files, values-dev, values-prod)
- A YAML file of settings (replicas, URLs, image tag) for one environment, which Helm fills into the chart's templates. Lesson 40.1
- values layer (values layers)
- One source of Helm values: chart defaults, the parent chart, each -f file, then --set flags by kind. Each overrides the one before. Lesson 40.21
- values.yaml (chart defaults)
- The chart's default values, its public settings. Values files and --set override them. Lesson 40.19
- variable scope (pipeline) (queue time)
- Where a pipeline variable is defined: pipeline, stage or job. The most specific wins; values set at queue time or by a script override the YAML. Lesson 40.7
- version range (~1.3.0, ^1.3.0, 20.x)
- A dependency rule like ~1.3.0 (patch updates only) or ^1.3.0 (anything below 2.0.0) instead of one exact version. Lesson 40.29
- with / range ({{ with }}, {{ range }})
- Template blocks: with X runs its body only if X is non-empty, with the dot set to X; range loops over a list or map (maps in sorted key order). Lesson 40.24
- workspace: clean (clean: all)
- A job setting that wipes the agent workspace first, so a self-hosted agent behaves like a fresh machine and proves the pipeline is reproducible. Lesson 40.9