I have been trying out draft builds in our koji instance.
The draft build, promote and setting up the extra acls to confine drafts to a particular tag are all working well.
When running "koji dist-repo" against a tag containing draft builds it fails very deliberately[1]. I was thinking to add
some other options --skip-draft, --with-draft options to "dist-repo" somewhat like is already present with "list-tagged" and "--draft" , "--no-draft". Motivation here is we have
always generated yumrepos of our build destination tags using dist-repo and that with the addition of a draft build this is currently not possible.
* "--skip-draft" would grab just latest non-draft builds. (The one we would actually use)
* "--with-draft" would grab latest builds which may be a draft. ( Probably would not use )
default behaviour could stay the same.
[1] https://pagure.io/koji/c/3b1df037be675dfd58e2385065e0f5cd576696a1
Koji 1.35.2 is out. Another minor update. So, the update should be
straightforward (no db schema changes) and safe for everybody. If
you've installed 1.35 or 1.35.1, an update is recommended as it contains few
minor regression fixes and improvements to the repo-on-demand
mechanism introduced in 1.35. As it is a longer time from latest minor
release, this one included more fixed issues than it is standard (30
issues).
Thanks to everyone who contributed!
You can read full release notes here:
https://docs.pagure.org/koji/release_notes/release_notes_1.35.2/
A few more important changes are part of this release:
#4228 - wait-repo behaves more compatible by default
#4207 - always preserve latest repo symlink
#4277 - separate thread for repo requests, so they are handled faster
You can view the 1.35.2 roadmap at https://pagure.io/koji/roadmap/1.35.2/
For the current roadmap, see https://pagure.io/koji/roadmap
You can download this and other releases at
https://pagure.io/koji/releases or PyPi.
See you again with major release 1.36 in a few months!
--
Tomas Kopecek <tkopecek(a)redhat.com>
RHEL Build Development, RedHat