TarGz Package API
Monteur natively supports
Gz for packaging
across various app variants that are compliant to existing programs. This recipe
allows the repository to seamlessly package
.tar.gz application in a highly
customizable manner easily and seamlessly.
The objective of distributing the recipe is simple: to make building
packages painlessly in a consistent manner with minimal to no further
All recipes are arranged based on its own semantic versioning and is not directly related to Monteur’s actual release version. Hence, feel free to explore each versions to suit your CI needs.
Here are the available Package API recipe for
.tar.gz integrations. Please
read through your selected version’s details on what has changed, what is
required, and how to customize and used them.
The arrangement are the latest at the top or first.
TarGz Package API is available for download here:
- You should download and place the recipe into your
<config>/package/jobs/directory with the name
- Once done, edit the configuration file for:
.tar.gzpackages list. Duplicate if there are more build variants to be packaged into
Packages.XXX.OS- list of supported operating system for this package.
Packages.XXX.Arch- list of supported CPU architecture for this package.
Packages.XXX.Name- filename without extension for this package.
Packages.XXX.Distribution- list of supported distributions.
Packages.XXX.BuildSource- instruct Monteur to package a source code pack or a binary pack (not both). If both are needed, duplicate the recipe since they are essentially 2 different packages.
[Packages.XXX.Files]- the list of files to be assembled by Monteur for packaging.
For detailed information about each fields, visit: Package Specification Data Structure for more info.
- Backward Compatible - Created the base TOML configuration recipe.
- Backward Compatible - Integrated with GitLab CI.
That’s all for Monteur operating
TarGz packaging. If you found a bug or have
any questions about the recipe, please feel free to raise your question at our