[Gluster-infra] separating code analysis from download

Michael Scherer mscherer at redhat.com
Thu Nov 5 12:08:05 UTC 2015

Le jeudi 05 novembre 2015 à 12:44 +0100, Niels de Vos a écrit :
> [fixed CC to gluster-devel at gluster.org]
> On Thu, Nov 05, 2015 at 06:13:52AM -0500, Kaleb KEITHLEY wrote:
> > <top post>
> > How about devel.gluster.org? Or upload.gluster.org?
> > 
> > Either one would be reasonable for nightly coverity/clang/etc reports as
> > well as community uploads?
> > 
> > </top post>
> devel.gluster.org sounds good to me. We will use it for uploading, but
> also downloading, unless the uploads get replicated to
> download.gluster.org and we use that as the only public accessible
> download system.

I am ok with that, but there is a risk of confusion with
dev.gluster.org :)

> The nightly builds used to get uploaded to download.gluster.org too. A
> replacement system (+user) for that needs to accept scp from
> build.gluster.org and be able to download the built packages from Fedora
> COPR (was using an lftp script for that).

I didn't think about this.

I would like to have it separate from the main download, so we could at
least avoid polluting the download stats ( since they were "skewed" by
some mirrors downloading all nightlies in the past ), and since we can
afford to lose the nightlies, IIRC.

But now, it depend on why do we use them, and what for.

Michael Scherer
Sysadmin, Community Infrastructure and Platform, OSAS

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://www.gluster.org/pipermail/gluster-infra/attachments/20151105/15cbe881/attachment.sig>

More information about the Gluster-infra mailing list