-
Notifications
You must be signed in to change notification settings - Fork 13
Use koji directly for release tasks #230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
903c0f5 to
2012bf2
Compare
2012bf2 to
d844ad5
Compare
d844ad5 to
6c9149e
Compare
|
Add some additional functionality per requests from @ekohl . There is now a task to verify a tag (or all tags. This done by examining all hosts and their associated tags and generating a list. The list of packages for the tag are checked in Koji and locally in git and then reports any differences detected. Most tag runs were about 40 seconds and |
858535c to
3f59335
Compare
3f59335 to
9ab6539
Compare
| when: diff_package_tags is defined | ||
| - role: build_package | ||
| when: diff_package_changed|bool | ||
| when: diff_package_changed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems to trigger 'diff_package_changed' is undefined ?!
9ab6539 to
1edbf29
Compare
1edbf29 to
e5d20a8
Compare
e5d20a8 to
e5b376d
Compare
e5b376d to
59fc21b
Compare
|
The part of this change dealing with renaming whitelist check to tag check has been split off #293 |
|
Mostly moved to here -- #303 |
The idea here is to move away from relying on tito releasers and whitelists and using package_manifest and koji directly for build tasks. Given this requires transition within a package_manifest I am attempting to build it such that both functionality is supported for some period of time based on available configuration in the package_manifest.