Working With Tags¶
Your Factory initially has a single branch,
By convention, Targets are tagged with the branches they are built from.
This means the Targets have the tag
For this tutorial, it is assumed you have created and worked on a
This has not yet been covered.
See the Factory Source Code reference manual on how to configure the CI with new branches.
This helps keep the development flow fast.
For example, you have
platform build based on
devel branch, and install it on the device.
Then you develop applications on
containers.git from the
The application is built by the CI with a
containers-devel trigger name and produces a Target tagged with
Finally, the device automatically updates to the latest Target tagged with
There are some use cases that you might want to control what tag a device follows, and Targets are tagged:
- Preventing a device from following a tag such as
devel, which is automatically created every time you change the
- Testing a specific Target on a specific device.
This tutorial will guide you through examples to help you understand how tags work.
Estimated Time to Complete this Tutorial: 20 minutes
- Create more
fioctlto Tag a specific Target.
- Configure the device to follow a specific tag.