On Wed, Nov 30, 2016 at 12:49 PM, Alfredo Deza <adeza@xxxxxxxxxx> wrote: > On Wed, Nov 23, 2016 at 3:15 PM, Alfredo Deza <adeza@xxxxxxxxxx> wrote: >> Starting next week we will start building binaries and repositories >> from the ceph-ci.git repo (https://github.com/ceph/ceph-ci). >> >> The current build process, which uses ceph.git will also continue at >> the same time, so there is >> enough time to transition over. >> >> This doesn't change anything for a developer except where it needs to >> push to get a repository >> with binaries for a given branch. >> >> After a week of correctly building from both repositories I will send >> a follow up email to warn of the change. > > Last night we enabled ceph-ci builds and I managed to get a > configuration setting wrong and builds got stuck. > > This has since been corrected and everything should be as normal. We > are working to enable the new ceph-ci builds this week. > > Sorry for any troubles. Is this just for the new Jenkins builds or are the gitbuilders being pointed at the ceph-ci repo (and/or the old repo) too? John >> >> Let me know if you have any questions, >> >> >> Thanks! > -- > 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
