release-engineering/tito
1
0
Fork 0
mirror of https://github.com/rpm-software-management/tito.git synced 2025-02-23 12:12:47 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
tito/rel-eng/releasers.conf

20 lines
625 B
Text
Raw Normal View History

Restructure release CLI.
2011-10-15 11:50:39 -03:00
[yum-f15-x86_64]
Allow setting specific builder and passing builder args on CLI. Can now build with a specific builder, and pass it required arguments. i.e. tito build --builder mock --builder-arg mock=fedora-16-x86_64
2011-10-15 16:55:28 -03:00
releaser = tito.release.YumRepoReleaser
Restructure release CLI.
2011-10-15 11:50:39 -03:00
builder = tito.builder.MockBuilder
Add new mechanism for passing custom arguments to builders. This is something to avoid using if possible, you wouldn't want to require these for a builder that's the default for your project, otherwise you'd need to specify it every time you ran the CLI. However builders like the mock builder need to know which mock config to use, and it could be multiple values for one project trying to do builds for multiple OSs. Adding a "builder.prop = value" to a releaser target section will pass the valie prop to the builder configured.
2011-10-15 16:00:01 -03:00
builder.mock = fedora-15-x86_64
Restructure release CLI.
2011-10-15 11:50:39 -03:00
rsync = fedorapeople.org:/srv/repos/candlepin/subscription-manager/fedora-15/x86_64/
Add a rsync username env variable for yum repo releaser.
2011-10-15 12:21:58 -03:00
Actually use releaser config instead of hardcoded values.
2011-10-15 12:52:03 -03:00
[yum-f16-x86_64]
Allow setting specific builder and passing builder args on CLI. Can now build with a specific builder, and pass it required arguments. i.e. tito build --builder mock --builder-arg mock=fedora-16-x86_64
2011-10-15 16:55:28 -03:00
releaser = tito.release.YumRepoReleaser
Add a rsync username env variable for yum repo releaser.
2011-10-15 12:21:58 -03:00
builder = tito.builder.MockBuilder
Add new mechanism for passing custom arguments to builders. This is something to avoid using if possible, you wouldn't want to require these for a builder that's the default for your project, otherwise you'd need to specify it every time you ran the CLI. However builders like the mock builder need to know which mock config to use, and it could be multiple values for one project trying to do builds for multiple OSs. Adding a "builder.prop = value" to a releaser target section will pass the valie prop to the builder configured.
2011-10-15 16:00:01 -03:00
builder.mock = fedora-16-x86_64
Actually use releaser config instead of hardcoded values.
2011-10-15 12:52:03 -03:00
rsync = fedorapeople.org:/srv/repos/candlepin/subscription-manager/fedora-16/x86_64/
[yum-el6-x86_64]
Allow setting specific builder and passing builder args on CLI. Can now build with a specific builder, and pass it required arguments. i.e. tito build --builder mock --builder-arg mock=fedora-16-x86_64
2011-10-15 16:55:28 -03:00
releaser = tito.release.YumRepoReleaser
Actually use releaser config instead of hardcoded values.
2011-10-15 12:52:03 -03:00
builder = tito.builder.MockBuilder
Add new mechanism for passing custom arguments to builders. This is something to avoid using if possible, you wouldn't want to require these for a builder that's the default for your project, otherwise you'd need to specify it every time you ran the CLI. However builders like the mock builder need to know which mock config to use, and it could be multiple values for one project trying to do builds for multiple OSs. Adding a "builder.prop = value" to a releaser target section will pass the valie prop to the builder configured.
2011-10-15 16:00:01 -03:00
builder.mock = epel-6-x86_64
Actually use releaser config instead of hardcoded values.
2011-10-15 12:52:03 -03:00
rsync = fedorapeople.org:/srv/repos/candlepin/subscription-manager/epel-6/x86_64/
Add new mechanism for passing custom arguments to builders. This is something to avoid using if possible, you wouldn't want to require these for a builder that's the default for your project, otherwise you'd need to specify it every time you ran the CLI. However builders like the mock builder need to know which mock config to use, and it could be multiple values for one project trying to do builds for multiple OSs. Adding a "builder.prop = value" to a releaser target section will pass the valie prop to the builder configured.
2011-10-15 16:00:01 -03:00
Reference in a new issue Copy permalink