Part 5: Trails #
Every time you execute a process represented by a Kosli Flow, you would initiate a trail to record the changes made during that specific execution.
You have the flexibility to determine the boundaries of what you consider a single execution of your process. For instance, in a software delivery process, an execution instance might be defined by:
- Git commits: the trail represents changes recorded from a single commit (as reported from CI).
- Pull requests: the trail represents changes recorded throughout the life of a single pull request (can span multiple commits).
- Jira or Github issues: the trail represents changes recorded throughout the life of a single ticket/issue (can span multiple pull requests and commits).
Each trail must possess a unique name within the Flow. This name typically follows a custom pattern, depending on how you define the scope of a single process execution.
Begin a trail #
To begin a Trail, you can run a command similar to the one below:
$ kosli begin trail trail-1 --flow process-1 --description "My first trail"
Rerunning the command with different description or template file will update the Trail.
See kosli begin trail for more details.
You can overwrite the flow template for each trail using --template-file.
By default, the trail inherits the template from its Flow.
