Re: [openstack-dev] [Ironic] Clarifications about ThirdParty CI deadlines
On Mon, Mar 7, 2016 at 1:48 PM, Thiago Paivawrote: > Hello folks, > > My project is in need of some clarifications about the deadlines for the > CI deployment on [1]. If you can kindly answer these questions to help us > consider changes on our sprint planning to address the community > requirements, would be very very helpful: > > 1) In the point 2, what do we mean by "receive events"? Is is about > reading from the event stream of Gerrit and take the appropriate actions? > Act upon "check experimental" or "check " comments are > considered valid to fulfill this requirement? > Just be able to connect to gerrit and receive events - see: http://docs.openstack.org/infra/system-config/third_party.html#reading-the-event-stream > > 2) We are a little confused with the phrase "post comments in the > sandbox". By that we mean commenting on the "openstack-infra/ci-sandbox" > project? Do we need to keep commenting on sandbox even when we have already > set-up the job to read events and comment results for the > "openstack/ironic" project? > > This is just a way to test your CI system without posting garbage to the ironic project patch comments. The sandbox is a place to post comments on a test pass and verify that it all llooks good and satisfies the requirements. See: http://docs.openstack.org/infra/system-config/third_party.html#testing-your-ci-setup Kurt Taylor (krtaylor) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ironic] Clarifications about ThirdParty CI deadlines
I'll try to answer your questions as best I can. As I understand it, "receive events" means that you can listen to the gerrit stream and take an action when for example a new patch is uploaded or a recheck comment is left etc. Initially we encourage people to get their CI listening to the ci-sandbox project for testing and making sure comments are pushed correctly etc, but once testing is complete and your happy to start receiving events from openstack/ironic you can switch over to that, there isn't a requirement to keep posting in the sandbox. Sam From: Thiago Paiva <thia...@lsd.ufcg.edu.br<mailto:thia...@lsd.ufcg.edu.br>> Reply-To: "OpenStack Development Mailing List (openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Date: Monday, 7 March 2016 19:48 To: "OpenStack Development Mailing List (openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [Ironic] Clarifications about ThirdParty CI deadlines Hello folks, My project is in need of some clarifications about the deadlines for the CI deployment on [1]. If you can kindly answer these questions to help us consider changes on our sprint planning to address the community requirements, would be very very helpful: 1) In the point 2, what do we mean by "receive events"? Is is about reading from the event stream of Gerrit and take the appropriate actions? Act upon "check experimental" or "check " comments are considered valid to fulfill this requirement? 2) We are a little confused with the phrase "post comments in the sandbox". By that we mean commenting on the "openstack-infra/ci-sandbox" project? Do we need to keep commenting on sandbox even when we have already set-up the job to read events and comment results for the "openstack/ironic" project? Thank you, [1] https://wiki.openstack.org/wiki/Ironic/Testing#Third_Party_CI_Requirements Thiago Paiva Brito Lead Software Engineer OneView Drivers for Openstack Ironic __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Ironic] Clarifications about ThirdParty CI deadlines
Hello folks, My project is in need of some clarifications about the deadlines for the CI deployment on [1]. If you can kindly answer these questions to help us consider changes on our sprint planning to address the community requirements, would be very very helpful: 1) In the point 2, what do we mean by "receive events"? Is is about reading from the event stream of Gerrit and take the appropriate actions? Act upon "check experimental" or "check " comments are considered valid to fulfill this requirement? 2) We are a little confused with the phrase "post comments in the sandbox". By that we mean commenting on the "openstack-infra/ci-sandbox" project? Do we need to keep commenting on sandbox even when we have already set-up the job to read events and comment results for the "openstack/ironic" project? Thank you, [1] https://wiki.openstack.org/wiki/Ironic/Testing#Third_Party_CI_Requirements Thiago Paiva Brito Lead Software Engineer OneView Drivers for Openstack Ironic __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev