On 07/02/2015 01:39 PM, Matthew Miller wrote:
On Thu, Jul 02, 2015 at 12:22:54PM -0500, Scott Collier wrote:
AIUI, this all goes through the Fedora-Dockerfiles repo. I don't
know what this would look like, but I'm envisioning the CentOS
Jenkins system pulling in this repo, and then running x scripts to
confirm things are working, based on some trigger. At that point,
maybe it sends an email out to a list for pass / fail? Which list?
These are details we will work out.
*nod* (And taking the test list off of the CC since the following
isn't a test discussion...)
I can't believe I didn't consult with you on the Layered Builds change
proposal, since you've been doing the Fedora Dockerfiles. Sorry — I
should have made sure you were included.
no problem. happy to participate in future discussions if needed.
As you've probably seen, the
change calls for "dist-git" style management of the dockerfiles, which
would mean one repo for each one, rather than one mega-repo — the
theory being that this can scale better and allow more independence.
I agree with this approach. I think it would encourage ownership as well.
This seemed like a good idea to me, but I hadn't really stopped to
consider the impact on the current Fedora Dockerfiles package. I guess
eventually it could be separated into various components
This could be done without to much trouble. Each directory in
Fedora-Dockerfiles stands on it's own. It would be a good starting
point for the eventual maintainer of each component. I do think it
would make sense to leave Fedora-Dockerfiles in some working state
moving forward for others to practice on. Unless there was some well
defined process for sharing the dist-git content. I'm not familiar with
dist-get.
— or in fact
could be the basis of an initial immediate set. What do you think?
Yup, could do that.
Another thing of note: we could talk with Infrastructure about adding
Pagure support to all the new dist-git repos, so they'd all have a web
based interface, pull requests, etc.
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
