tito.props - Man Page
directives for tito(5) how to build package.
Project settings can be stored in files:
The global .tito/tito.props is generally where settings are defined. For some multi-project git repositories, individual packages can override these settings by placing a tito.props in the project directory. (i.e. same location as it’s .spec file)
tito.props can contain several sections:
This section and a couple of its properties are required. You can use following variables:
The fully qualified Builder class implementation to use. You can either specify builders shipped with tito(5) (see Builders section below), or a custom builder located within the directory your lib_dir option points to. This property is required.
The fully qualified Tagger class implementation to use. You can either specify taggers shipped with tito(5) (see Taggers section below), or a custom tagger located within the directory your lib_dir option points to. This property is required.
Optional property defining a directory to be added to the Python path when executing tito. Allows you to store custom implementations of Builder, Tagger, and Releaser.
This option is used to control the formatting of entries when generating changelog entries. The default value is "%s (%ae)". See PRETTY FORMATS in git-log(1) for more information.
If set to 0, then entries in changelog (subject of commits) are not followed by email of committer. Default is 1. This option is deprecated and provided for backwards-compatibility only. New configurations should consider changelog_format instead.
If set to 0, it will not remove from cherry picked commits the part "(cherry picked from commit ...)"
By default, changelog dates don’t contain time (e.g. Wed Nov 1 2017). When this option is set to True, changelog entries are generated in a datetime format (e.g. Wed Nov 1 11:08:13 EDT 2017). This feature requires RPM 4.14, therefore it is supported only on Fedora 27, EPEL8, openSUSE Leap 15 and higher.
An optional specification of a suffix to append to all tags created by tito for this repo. Can be useful for situations where one git repository is inheriting from another, but tags are created in both. The suffix will be an indicator as to which repo the tag originated in. (i.e. tag_suffix = -mysuffix)
This option is used control the text of git commit message that is used when new tag is generated. You can use "%(name)s", "%(release_type)s" and "%(version)s" placeholders.
This option controls the format used in VersionTagger. If not specified other taggers.
This boolean enables GnuPG signed tags using git tag -s.
If true, download sources from predefined Source<N> addresses to the SOURCE folder.
Koji and Copr
Dist tag variable, which is passed to rpmbuild for packages build in this tag.
Space separated list of packages, which should not be built in this tag.
If whitelist is present, only packages listed here can be built in this tag. This also override blacklist.
Specify name of Software Collection into which package should be build.
Allows the user to write out a template file containing version and/or release and add it to git during the tagging process.
Path to a file conforming to a Python string.Template, as described at http://docs.python.org/2/library/string.html#template-strings. Path is relative to root of the entire git checkout, as this is likely to be stored in the top level .tito directory. The variables $version and $release are available inside the template.
Specifies a file to write, relative to the directory for the package being tagged.
[version_template] destination_file = version.txt template_file = .tito/templates/version.rb
If tito is older then specified version, it will refuse to continue.
Comma separated list of packages, which needs to be installed prior tagging. If those packages are not installed, tito will refuse to continue.
Basic package builder. It create tar.gz of whole directory and create src.rpm and build rpm using some supported method.
Use mock instead of rpmbuild for building an RPM package. See doc/builders.md.
Builder for packages that do not require the creation of tarball. Usually these package have source files checked directly into git.
Builder for packages that are based off an upstream git tag. Commits applied in downstream git become patches applied to the upstream tarball. For example - you are building package foo-1.2-3... Tar.gz file is created from commit, which is tagged by foo-1.2-1 and the diff between release 1 and 3 is put in spec file as Patch0.
Builder for packages that list a .gem as Source0, the .gemspec shares a directory hierarchy with the .spec file and the upstream does not want to check .gem files into their git repository.
Behave similar as tito.builder.UpstreamBuilder, but patch is created for every release. Therefore package from previous example will end up with tar.gz file created from tag foo-1.2-1 and with Patch0: foo-1.2-1-to-foo-1.2-2.patch Patch1: foo-1.2-1-to-foo-1.2-3.patch
[builder] fetch_strategy = tito.builder.fetch.ArgSourceStrategy
ArgSourceStrategy here could be replaced with a custom strategy if you were to have one in your lib_dir.
Builder for packages with existing tarballs checked in using git-annex, e.g. referencing an external source (web remote). This builder will "unlock" the source files to get the real contents, include them in the SRPM, then restore the automatic git-annex symlinks on completion.
All taggers which inherit from tito.tagger.VersionTagger (all to this date), will update file GITROOT/.tito/packages/name-of-package and put there one line which consist of version-release of package, space delimiter, path to package directory relative to GITROOT.
Standard tagger class, used for tagging packages build from source in git. Release will be tagged by incrementing the package version, and the actual "Release" will be always set to 1.
Keep version and increment release.
It is used for EUS packages.
Tagger which is based on ReleaseTagger and uses Red Hat Enterprise Linux changelog format:
- Resolves: #1111 - description
- Related: #1111 - description
You can create section with the name same as releaser target and there you can specify this option:
This is useful for FedoraGitReleaser and DistGitReleaser and will allow you to specify name of remote dist-git branch.
For example let say you have in releaser.conf: [git-sat] releaser = tito.release.DistGitReleaser branches = satellite-6.0-rhel-6
and then you can add remote_git_name: [git-sat] releaser = tito.release.DistGitReleaser branches = satellite-6.0-rhel-6 remote_git_name = ruby193-rubygem-simple-navigation And it will push package into ruby193-rubygem-simple-navigation dist-git despite the fact that it is in /rubygem-simple-navigation directory. And project name (as taken from spec file) is rubygem-simple-navigation.
Tagger which is based on VersionTagger and deal with SUSE / OBS specific separate changes file and format.
[buildconfig] builder = tito.builder.Builder tagger = tito.tagger.VersionTagger
[koji] autobuild_tags = dist-5E-sw-1.2-candidate dist-f12-sw-1.2-candidate dist-f13-sw-1.2-candidate
[dist-5E-sw-1.2-candidate] disttag = .el5
[dist-f12-sw-1.2-candidate] disttag = .fc12 blacklist=jabberd-selinux
[dist-f13-sw-1.2-candidate] disttag = .fc13 blacklist=jabberd-selinux
Devan Goodwin <email@example.com>
James Bowes <firstname.lastname@example.org>
Jesus M Rodriguez <email@example.com>
Pall Sigurdsson <firstname.lastname@example.org>
Miroslav Suchý <email@example.com>
and: Adam Miller, Alex Wood, Aron Parsons, Brenton Leanhardt, Ivan Nečas, John Eckersberg, Kenny MacDermid, Lukáš Zapletal, Luke Meyer, Marian Csontos, Martin Bačovský, Michael Stead, Mike McCune, mscherer, Paul Morgan, Sean P. Kane, Steve Ashcrow Milner