On Sat, Aug 10, 2019 at 2:13 AM Mingshen Sun <b...@mssun.me> wrote: > > > > == Continuous Integration Service == > > > > > > MesaTEE currently uses self-hosted continuous integration (CI) service > > > which can > > > help developers to automatically test commits. The CI service involves > > > several > > > nodes which support Intel SGX. We would like to continue doing so. > > > > This may not be possible, what would the project do if that was the case? > > Have you discussed this with your proposed mentors or infra? > > About the CI infrastructure, actually, the "self-hosted CI" is not our > internal infra, we are using a open source CI service (Drone CI) with > our servers/NUC with SGX supported. To answer your questions, we have > several solutions: > - we can use simulation mode for basic CI testing (by using existing > infra in Apache for example). And before merging a pull request, full > testing on a SGX supported machine is required > - donating our SGX machines for CI services to Apache is another > option we may consider, but this should be further discussed >
I don't see the hosting of CI on an external service or hardware as a big issue, we have a lot of projects that are currently using Travis CI, and others, like Spark, running their CI on a bunch of machines hosted at Berkley. Having said that, I believe the results of the CI (e.g. log, etc) should be visible to all which is what happens with Travis CI and the spark ci today. Having said that, all the possible next steps mentioned above are also possible, but IMHO not a requirement. -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
