<tt><font size=2>amessina@messinet.com wrote on 11/04/2013 18:56:08:<br>
> <br>
> On Monday, November 04, 2013 05:28:28 PM John.Florian@dart.biz wrote:<br>
> > From what I gather, mash is the tool of choice for composing
usable<br>
> > repositories out of koji's build efforts. What advice do
y'all have for<br>
> > integrating the two? Presently, I've got mash running via
cron every 15m<br>
> > but that hardly seems optimal as it's a lot of busy work if I'm
not<br>
> > building packages for several days and conversely adds more latency
into my<br>
> > build + deploy + test timeline if a build finishes right after
mash does.<br>
> > Seems like a hook or callback is in order, but I've not
seen any write ups<br>
> > on this subject. Also, I had a rpm built by koji which
then made it over<br>
> > to my repo via mash, but then I got busy for a few days on other
tasks.<br>
> > When I came back it appears that my rpm has disappeared
from the repo.<br>
> > I'm guessing kojira cleaned it up, but I was under the
impression that<br>
> > such cleanup wouldn't propagate to the repo.<br>
> <br>
> I use a very custom koji-maint [1] script, but you could take a look
at the <br>
> mashCreateRepos function for some ideas. I run it from a systemd
timer unit <br>
> once a day. You could have systemd run it more often if you
wanted,since the <br>
> design goal was to only have mash create new repositories *if* the
file date <br>
> from the previously created repo is older that the last package tagged
in the <br>
> specific Koji build target.<br>
> <br>
> -A<br>
> <br>
> 1. </font></tt><a href="https://messinet.com/trac/browser/koji-maint/koji-maint"><tt><font size=2>https://messinet.com/trac/browser/koji-maint/koji-maint</font></tt></a><tt><font size=2><br>
> <br>
> -- <br>
> Anthony - </font></tt><a href=http://messinet.com/><tt><font size=2>http://messinet.com</font></tt></a><tt><font size=2>
- </font></tt><a href=http://messinet.com/~amessina/gallery><tt><font size=2>http://messinet.com/~amessina/gallery</font></tt></a><tt><font size=2><br>
> 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E<br>
</font></tt>
<br><font size=2 face="sans-serif">Thanks for that link. Looks to
have all sorts of handy features. Package signing is another item
on my checklist and I see you've got code in there for that too. I'll
have to hack on this (or so it appears) to get it working with certificate-based
authentication. Would you be interested in any such patches?</font>
<br><font size=2 face="sans-serif"><br>
--<br>
John Florian</font>
<br>