On Thu, Oct 6, 2016 at 5:43 PM, Alfredo Deza <adeza@xxxxxxxxxx> wrote: > Hi all, > > The (current) behavior with gitbuilders is that it builds every commit > of every branch in Github. > > With the new CI system, although we can cope with the demand as the > Ceph project grows in contributions, we are planning on only building > branches that really need to be built. > > This keeps the whole system going as fast as possible (we are > currently getting full repositories in about 1 hour) and very > efficient. > > We need to come up with a naming convention for branches to be built. > At the moment we are building everything and that is preventing us > from enabling other features in the system like all the other > "flavors" (e.g. tcmalloc). > > Branch names for builds will need certain restrictions. Because the > system is based on HTTP components, no HTTP reserved chars can be used > (e.g. historic/libradosgw would be a no-go). Other invalid chars are: > & , ; ? = + $ : > > We could keep the implicit convention for `wip-*` or maybe something similar? Building everything that starts with wip-* sounds fine to me. But isn't that usually everything that we push to the ceph/ceph repository? What is is that we're trying to avoid building? John > Ideas welcomed :) > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
