Koji 1.7.1 is tagged and posted.
* Mon Nov 19 2012 Mike McLean <mikem at redhat.com> - 1.7.1-1 - improved upload mechanism - koji-shadow enhancements - handle multiple topurl values in kojid - fix form handling - mount all of /dev for image tasks - avoid error messages on canceled/reassigned tasks - handle unauthenticated case in moshimoshi - fix the tag_updates query in tag_changed_since_event - stop tracking deleted repos in kojira - don't die on malformed tasks - fix bugs in our relpath backport - avoid baseurl option in createrepo - message bus plugin: use timeout and heartbeat - add maven and win to the supported cli search types - remove latest-by-tag command - fix noreplace setting for web.conf - add sanity checks to regen-repo command - debuginfo and source options for regen-repo command - make taginfo command compatible with older koji servers
A few entries deserve further explanation:
1) improved upload mechanism
The new upload mechanism avoids the overhead of xmlrpc and base64 encoding. Depending on other factors this can make for a tremendous speed improvement. It also reduces cpu load on the hub.
The boolean use_fast_upload config option for the cli and kojid controls whether the new mechanism is used. This defaults to True for kojid (which is assumed to be talking to a matching kojihub) and False for the cli (which might be talking to an older hub).
2) handle multiple topurl values in kojid
You can now provide multiple topurl values in kojid.conf, e.g.
topurl=http://hub.example.com/kojifiles http://hub2.example.com/kojifiles
If you do, then kojid will generate multiple baseurls for the mock config files it generates.
We do not (yet) do anything else with the extra topurl values. For other places where we use topurl, only the first matters.
Hi Mike,
First, thanks for this new release!
- remove latest-by-tag command
I've just read your changelog for 1.7.1. I am still using 1.6.0 and plan to update soon. However, we use 'latest-by-tag' command but based on your comment it looks like it will break some of our internal processes relying on 'latest-by-tag :(
So I am wondering why it has been removed and if there is a replacement for it ?
Cheers, Thomas
On 12/02/2012 11:31 PM, Thomas Guthmann wrote:
- remove latest-by-tag command
I've just read your changelog for 1.7.1. I am still using 1.6.0 and plan to update soon. However, we use 'latest-by-tag' command but based on your comment it looks like it will break some of our internal processes relying on 'latest-by-tag :(
So I am wondering why it has been removed and if there is a replacement for it ?
The latest-by-tag command produced misleading, incomplete reports. It was a broken mess founded on a misunderstanding of Koji's data structure.
If your processes were relying on latest-by-tag, then they were already broken ;)
What folks should do instead is: - pick a list of tags they care about - query for the latest builds of package X in those tags
e.g. # for tag in $MYTAGS; do koji list-tagged --quiet --latest --inherit $tag $MYPKG; done
I am open to adding more reports if there is a real need, but latest-by-tag was beyond fixing.
Hi Mike,
[..]
The latest-by-tag command produced misleading, incomplete reports. It was a broken mess founded on a misunderstanding of Koji's data structure.
Ok.
What folks should do instead is:
- pick a list of tags they care about
- query for the latest builds of package X in those tags
e.g. # for tag in $MYTAGS; do koji list-tagged --quiet --latest --inherit $tag $MYPKG; done
Ok, that will do. Thanks for your help.
Thomas
buildsys@lists.fedoraproject.org