www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Gruno (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (INFRA-11429) Apache CloudStack - Continuous Integration Support
Date Fri, 11 Mar 2016 08:09:40 GMT

     [ https://issues.apache.org/jira/browse/INFRA-11429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Daniel Gruno closed INFRA-11429.
    Resolution: Later
      Assignee: Daniel Gruno

Hi Will,
We've had a discussion about what strategy to pursue here, and I'm afraid we're going to have
to close this as 'Later' for the time being. Personal, organisation-wide tokens is not something
we are prepared to hand out to individuals (we only do that for official, sanctioned applications
on our short-list). As we cannot grant just status permissions to users due to the coarseness
of GitHub's ACL, this isn't an option either.

We are exploring a 'git-dual' approach at the moment, which would provide write access to
committers on GitHub (codename: MATT). This experiment is going very well, but it is still
a little while away, possibly a month or two before we are comfortable adding TLPs to it.

Another solution would be to have MATT be a gateway to this, wherein you get a token for MATT
for these operations and MATT (which has access to the repos) performs the necessary operations.
We discussed this at length, and are not comfortable adding yet another service we need to
support, given that the experiment is likely to yield write-access very soon. Once you add
a service, it's there - and we already have 150+ of those to maintain with just 3 full-time

I hope you understand our reasoning, and I hope the project can arm itself with a bit of patience
as we prepare for the possible write-access very soon.

> 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
>            Assignee: Daniel Gruno
>            Priority: Minor
> 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 <wstevens@cloudops.com>
> Paul Angus <paul.angus@shapeblue.com>
> Bharat Kumar <bharat.kumar@accelerite.com>
> Remi Bergsma <RBergsma@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

View raw message