Key Concepts
Template
Stage
Script
Trigger Config
Required Permissions
Template Types
Template Requirements
Templates can specify which features a project must have configured:Deployment Kinds
Templates support different deployment strategies:How to Create a Template
Click Add Template
Configure General Settings
Set Requirements
Configure Helm Defaults (Optional)
Add Stages
Add Scripts
Configure Triggers
Save
How to View a Template
Find the Template
Click View
Browse Tabs
How to Edit a Template
Find the Template
Open Detail Page
Modify Settings
Save
How to Duplicate a Template
Find the Template
Click Duplicate
Review
Rename
How to Delete a Template
Find the Template
Click Delete
Confirm
Managing Stages
Adding a Stage
Open Stages Tab
Click Add Stage
Configure Stage
Save
Stage Properties
Reordering Stages
Change the order value for each stage to control execution sequence. Stages execute in ascending order (1, 2, 3…).Managing Scripts
Adding a Script
Open Scripts Tab
Click Add Script
Configure Script
Save
Script Properties
Configuring Trigger Rules
Trigger Configuration Format
Trigger rules are defined in YAML format and control when pipelines are triggered by webhooks.Trigger Events
Branch Patterns
Use glob patterns for flexible branch matching:Using Preview
The Preview tab generates sample.kodeshift configuration files based on the template settings.
Open Preview Tab
Configure Parameters
Generate Preview
Review Output
Troubleshooting
Cannot edit template
Cannot edit template
- System templates cannot be edited; duplicate first
- Verify you have write permission
- Check if another user is editing the template
Cannot delete template
Cannot delete template
- System templates cannot be deleted
- Verify you have delete permission
- Try refreshing the page
Stages not executing in order
Stages not executing in order
- Verify stage order numbers are correct
- Lower numbers execute first
- Check if stages are marked as active
Scripts not applying to pipeline
Scripts not applying to pipeline
- Verify script provider type matches project provider
- Check script key is correctly referenced
- Ensure script is saved
Trigger not firing
Trigger not firing
- Verify YAML syntax is valid
- Check branch patterns match your branches
- Ensure webhook is configured for the repository
- Verify event type is included in trigger config
Preview not generating
Preview not generating
- All required parameters must be selected
- Template must have at least one stage
- Check for validation errors in other tabs
FAQ
What's the difference between system and custom templates?
What's the difference between system and custom templates?
How do I create a template from an existing project?
How do I create a template from an existing project?
Can I have multiple trigger configs in one template?
Can I have multiple trigger configs in one template?
What happens if I update a template used by existing projects?
What happens if I update a template used by existing projects?
How do I test a template before using it?
How do I test a template before using it?
Can scripts reference template variables?
Can scripts reference template variables?
What's the maximum number of stages in a template?
What's the maximum number of stages in a template?
Best Practices
Template Design
- Create templates for common workflow patterns
- Keep templates focused on specific use cases
- Use descriptive names and descriptions
- Document template requirements clearly
Stages
- Order stages logically (build → test → deploy)
- Use consistent naming across templates
- Keep stage count manageable (3-5 stages typical)
- Disable stages instead of deleting when debugging
Scripts
- Write provider-agnostic scripts when possible
- Use script keys that describe the action
- Keep scripts modular and reusable
- Test scripts independently before adding to templates
Trigger Configuration
- Use specific branch patterns over wildcards
- Map environments appropriately for each branch
- Include only necessary event types
- Document trigger behavior in template description
Organization
- Prefix template names with team or purpose
- Use icons to visually categorize templates
- Review and update templates periodically
- Remove unused custom templates