Thank you Will. (sorry been on holiday for a week)
I'm about to start a sprint with some of my colleagues to assist with the CI work..... I've just looked in Jira and there are 47 open tickets against Marvin right now [1], and I know I'm about to add a whole lot more. We're going to need some effort to triage the existing tickets and then fix the remaining tickets and any new ones. [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20marvin%20ORDER%20BY%20priority%20DESC [ShapeBlue]<http://www.shapeblue.com> Paul Angus VP Technology , ShapeBlue d: +44 203 617 0528 | s: +44 203 603 0540<tel:+44%20203%20617%200528%20|%20s:%20+44%20203%20603%200540> | m: +44 7711 418784<tel:+44%207711%20418784> e: paul.an...@shapeblue.com | t: @cloudyangus<mailto:paul.an...@shapeblue.com%20|%20t:%20@cloudyangus> | w: www.shapeblue.com<http://www.shapeblue.com> a: 53 Chandos Place, Covent Garden London WC2N 4HS UK [cid:image3f3e2f.png@1c68216f.43b51f60] Shape Blue Ltd is a company incorporated in England & Wales. ShapeBlue Services India LLP is a company incorporated in India and is operated under license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is a registered trademark. This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Shape Blue Ltd or related companies. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. -----Original Message----- From: williamstev...@gmail.com [mailto:williamstev...@gmail.com] On Behalf Of Will Stevens Sent: Thursday, March 10, 2016 11:04 PM To: dev@cloudstack.apache.org Subject: Re: [PROPOSAL] Minimum Viable CI Integration I have made the request. Here is the Jira ticket: https://issues.apache.org/jira/browse/INFRA-11429 Here is the content of the request... --- This request is for personal access tokens with the following permission be added to the https://github.com/apache/cloudstack repository in order for the apache cloudstack community to be able to implement Continuious Integration. Permission: (https://github.com/settings/tokens) - `repo:status` - Grants read/write access to public and private repository commit statuses. This scope is only necessary to grant other users or services access to private repository commit statuses without granting access to the code. With this permission the token owner will be able to view the apache/cloudstack repo and will be able to create and update the status of a pull request. This is the same type of permission used by the current TravisCI integration, but will allow the community to feedback the status of distributed CI runs on physical hardware. Here is more detail on the Status functionality: https://developer.github.com/v3/repos/statuses/ We would like the following apache/cloudstack community members be sent their own personal access tokens since they will be providing physical hardware for doing CI for apache/cloudstack and would like the results of these CI runs to be posted back to the community so the release managers on the project can better assess the impact of the different pull requests. Will Stevens <wstev...@cloudops.com> Paul Angus <paul.an...@shapeblue.com> Bharat Kumar <bharat.ku...@accelerite.com> Remi Bergsma <rberg...@schubergphilis.com> By providing each individual their own access token, you maintain fine grain control of their access to modify pull request statuses from their CI and you can revoke individual tokens if there is ever a concern. Some more context around this request... The Apache CloudStack community has been struggling with code quality issues due to the lack of CI and the wide breadth of features. Because of the scale of the project, no single organization or community member has the hardware to fully test the extent of the functionality provided by the product. This in combination with the attempt to increase the release cadence, the lack of full CI coverage is becoming a painful reality. I have developed a very simple CLI tool called `upr` ( https://github.com/swill/upr) which can be easily integrated into any CI implementation used by the different organizations/individuals to post back the status of their CI runs to the community. Please feel free to engage with us on the dev@cloudstack.apache.org mailing list if anything is unclear or if you have questions. --- *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ Find out more about ShapeBlue and our range of CloudStack related services: IaaS Cloud Design & Build<http://shapeblue.com/iaas-cloud-design-and-build//> | CSForge – rapid IaaS deployment framework<http://shapeblue.com/csforge/> CloudStack Consulting<http://shapeblue.com/cloudstack-consultancy/> | CloudStack Software Engineering<http://shapeblue.com/cloudstack-software-engineering/> CloudStack Infrastructure Support<http://shapeblue.com/cloudstack-infrastructure-support/> | CloudStack Bootcamp Training Courses<http://shapeblue.com/cloudstack-training/>
