On Monday, November 04, 2013 05:28:28 PM [email protected] wrote: > From what I gather, mash is the tool of choice for composing usable > repositories out of koji's build efforts. What advice do y'all have for > integrating the two? Presently, I've got mash running via cron every 15m > but that hardly seems optimal as it's a lot of busy work if I'm not > building packages for several days and conversely adds more latency into my > build + deploy + test timeline if a build finishes right after mash does. > Seems like a hook or callback is in order, but I've not seen any write ups > on this subject. Also, I had a rpm built by koji which then made it over > to my repo via mash, but then I got busy for a few days on other tasks. > When I came back it appears that my rpm has disappeared from the repo. > I'm guessing kojira cleaned it up, but I was under the impression that > such cleanup wouldn't propagate to the repo.
I use a very custom koji-maint [1] script, but you could take a look at the mashCreateRepos function for some ideas. I run it from a systemd timer unit once a day. You could have systemd run it more often if you wanted, since the design goal was to only have mash create new repositories *if* the file date from the previously created repo is older that the last package tagged in the specific Koji build target. -A 1. https://messinet.com/trac/browser/koji-maint/koji-maint -- Anthony - http://messinet.com - http://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E
signature.asc
Description: This is a digitally signed message part.
-- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
