On Fri, Jun 15, 2018 at 12:09:39PM +0200, Andrea Bolognani wrote: > On Fri, 2018-06-15 at 10:05 +0100, Daniel P. Berrangé wrote: > > On Fri, Jun 15, 2018 at 09:06:52AM +0200, Andrea Bolognani wrote: > > > libvirt.git feels like a sensible enough place to store these > > > files, especially considering that we've been storing pretty > > > much the same information in .travis.yml up until now; that > > > said, I don't love the idea of tracking what is ultimately > > > generated data, so I'm open to creating a separate, ad-hoc > > > repository (libvirt-dockerfiles.git?) instead. > > > > They really should be just generated directly by a script in > > the libvirt-jenkins-ci repo, we don't need to check the > > generated files into git anywhere IMHO. > > We *do* need to have the Dockerfiles committed *somewhere* for > Docker Hub automated builds to work. Does docker hub only pull from git repos, or does it have other options for detching the files ? Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
