[jira] [Comment Edited] (INFRA-11429) Apache CloudStack - Continuous Integration Support

["Will Stevens (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/INFRA-11429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190443#comment-15190443 ] 

Will Stevens edited comment on INFRA-11429 at 3/11/16 4:13 AM:
---------------------------------------------------------------

Github does have the granularity to only authorize `repo:status`, but it applies to all repositories.  This is how it works for all applications.  Since this is the same as all other application integrations, I don't think that should be an issue.  Thank you for looking into this for us.


was (Author: wstevens):
Github does have the granularity to only authorize `repo:status`, but it applies to all repositories.  This is how it works for all applications.  Since this is the same as all other application integrations, I don't think that should be an issue.

> Apache CloudStack - Continuous Integration Support
> --------------------------------------------------
>
>                 Key: INFRA-11429
>                 URL: https://issues.apache.org/jira/browse/INFRA-11429
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>         Environment: Github: https://github.com/apache/cloudstack
>            Reporter: Will Stevens
>
> 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 <ws...@cloudops.com>
> Paul Angus <pa...@shapeblue.com>
> Bharat Kumar <bh...@accelerite.com>
> Remi Bergsma <RB...@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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)