Appearance
Job Templates
Job templates let admins maintain reusable job blueprints and create linked jobs from them.
Use a template when several jobs should share the same workflow, but still need different values such as service names, image tags, paths, compose files, or target-specific labels.
For example, a Docker service update workflow reused for Ordyn api, frontend, edge, cache, net, SNMP, and Telematik services
In the frontend, templates live under Operations > Job Templates.
Creating templates
Create a template under Operations → Job Templates, or use Create template from job on an existing job. Choose endpoint or infrastructure scope and configure the shared workflow. Infrastructure templates select a Runner pool.
Define template inputs for values that differ between linked jobs. Reference them in supported fields with {{ template.parameter_name }}.
Creating linked jobs
Create linked jobs from the template and fill their inputs. Run and assign those jobs through the normal workflow for their scope. Editing the template changes the shared workflow used by its linked jobs.
What the template controls
The template owns the shared execution behavior of linked jobs:
- shared task workflow, including Cleanup
- execution scope
- Runner pool for infrastructure templates
- build features for infrastructure templates
- timeouts and validity windows
- endpoint requirements, execution type, shutdown policy, concurrency, desktop execution, and user interaction for endpoint templates
Change these values on the template when the shared workflow should change for every linked job that uses it.
What the linked job controls
Each linked job owns the values that make that job useful in a specific place:
- job name, friendly name, and description
- job folder
- schedules and event automations
- endpoint assignments, composition usage, and self-service presentation for endpoint linked jobs
- template input values
Edit the shared task workflow on the template.
Sharing build features
Configure shared build features under Features on an infrastructure template. Linked jobs inherit these settings and can override or disable individual features. An override replaces the feature's complete configuration.
The Isolated build network setting accepts template inputs and run-start variables.
Use template inputs for settings that differ between jobs. For example, define an Entity input named repository with kind Git repository, then use {{ template.repository }} as the Git source's repository.
Template inputs
Templates define named inputs. Supported input value types are:
stringselectnumberbooleanjsonentity
Use json for structured values such as arrays or objects, for example a list of Docker images.
Use entity to select a reusable resource, such as a Git repository.
Use select to offer a fixed list of choices.
Inputs can also have operator-facing labels, descriptions, defaults, and required flags.
Use template inputs for values that should differ between linked jobs. Examples include:
- service name
- Docker image list
- Docker tag variable key
- base path
- compose file name
- signature public key path
Variables inside template inputs
Entity, Number, Boolean, and Select inputs accept whole-field references to configured, non-secret variables, such as {{ vars.repository }}. These inputs cannot depend on values supplied or produced during a run.
String and JSON inputs can also use runtime expressions supported by the destination field. Build features can use non-secret variables available before steps run.
For example, a template can define a task path as:
text
{{ template.base_path }}/{{ template.compose_file }}One linked job can then set:
text
base_path = {{ vars.ordyn_frontend_base_path }}
compose_file = {{ vars.ordyn_frontend_compose_file }}Editing templates and linked jobs
Edit the template when you want to change the shared workflow.
Edit a linked job when you want to change that job's name, description, folder, schedules, automations, scope-specific usage settings, or template input values.
The template detail page shows jobs that were created from the template. A linked job's overview links back to its template.
Copying linked jobs
Copying a linked job creates a standalone job copy.
The copied job is independent from the template. Use this when you want to branch from a template-based job and then manage the copy independently.
Create another linked job from the template when you want that job to continue using the template.
Example
A template for Ordyn service container updates might define inputs like:
json
{
"service_name": {
"type": "string",
"label": "Service name",
"required": true
},
"base_path": {
"type": "string",
"label": "Base path",
"required": true
},
"compose_file": {
"type": "string",
"label": "Compose file",
"default": "compose.yml",
"required": true
},
"images": {
"type": "json",
"label": "Images",
"required": true
},
"tag": {
"type": "string",
"label": "Docker tag",
"required": true
}
}The template can then use those values in job fields and task payloads:
text
Update {{ template.service_name }}
{{ template.base_path }}/{{ template.compose_file }}
{{ template.images }}
{{ template.tag }}When creating a linked job, the template input values may still point to runtime variables:
json
{
"service_name": "Ordyn Frontend",
"base_path": "{{ vars.ordyn_frontend_base_path }}",
"compose_file": "{{ vars.ordyn_frontend_compose_file }}",
"images": [
"docker.hank-it.com/ordyn/frontend"
],
"tag": "{{ vars.ordyn_frontend_tag }}"
}When to use templates
Use job templates when:
- several jobs should share the same execution workflow
- each linked job needs a small set of different values
- workflow changes should be maintained in one template
- the resulting jobs still need the scheduling, automation, run history, and audit behavior available to their execution scope
Use a normal job without a template when the workflow is unique or unlikely to be reused.
Use composition tasks in a parent job when the problem is rollout order, batching, or staged execution across endpoint sets rather than sharing one task tree.