On 11/04/2013 05:28 PM, john.flor...@dart.biz 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.
You might consider mimicking kojira. That is, monitor the tags you care about for changes and only regenerate when you need to. It's not a perfect system, but it's much better than every X minutes. > Seems like a hook or callback is in order, but I've not seen any > write ups on this subject. That is also a possibility. The hub code has plenty of callback hooks. > 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 guess that depends on how the repo is generated. If the mash copies them rpms to its own location, then nothing in koji should touch them. If OTOH mash references the koji path directly in the generated repo, then the file could disappear if koji deletes it. (koji builds are generally deleted by koji-gc. kojira doesn't delete builds, it just manages yum repos) -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys
