DevHeads.net

Tagging commit hashes of Koji builds in dist-git

Is there a reason why we do not tag dist-git commits, using a name which
is derived from the NEVR from a Koji build?

How well does Git scale with thousands of tags?

Thanks,
Florian

Comments

Re: Tagging commit hashes of Koji builds in dist-git

By King InuYasha at 06/06/2019 - 08:10

On Thu, Jun 6, 2019 at 7:53 AM Florian Weimer < ... at redhat dot com> wrote:
We used to back in the CVS days, because we needed it for plague. Koji
blocks duplicate submissions anyway, so it stopped being needed when
we transitioned to Git.

We're going to probably introduce it for some automation in the near
future, though.

Git is not great with thousands of any kind of refs, be it branches or
tags. It still works, it's just things like 'git log' get kind of
expensive.

Re: Tagging commit hashes of Koji builds in dist-git

By Pierre-Yves at 06/06/2019 - 08:08

On Thu, Jun 06, 2019 at 01:52:20PM +0200, Florian Weimer wrote:
One of the issue is that currently tags are not immutable, ei packagers could
override them.

Pierre

Re: Tagging commit hashes of Koji builds in dist-git

By Thomas Moschny at 06/06/2019 - 09:41

Am Do., 6. Juni 2019 um 14:12 Uhr schrieb Pierre-Yves Chibon
< ... at pingoured dot fr>:
Tags could be signed, and also pagure could reject removal of tags.
Immutability is a feature of the repository, not the tags themselves,
I think.

- Thomas

Re: Tagging commit hashes of Koji builds in dist-git

By Igor Gnatenko at 06/06/2019 - 08:04

We actually talked about this on oSC19 with Neal Gompa and Florian
Festi. And we'd need it for automation we are planning to work on...
Then I spoke to pingou and he told me that tags are easy to delete and
you need some special hook to prevent that...

I did not have time to look at it though.

On Thu, Jun 6, 2019 at 2:02 PM Florian Weimer < ... at redhat dot com> wrote: