CircleCI Ideas

Make CircleCI to be available for use for Apache repositories

Currently CircleCI requires write access to the org webhooks. Apache INFRA can't allow it.
Therefore adding some flexible management of permissions can solve this issue. And a bunch of Apache projects can enable usage of this CI. [1-6] 
The other way is migrating for CircleCI from OAuth Apps to GitHub Apps (similar to TravisCI for opensource) [7]

[1] https://issues.apache.org/jira/browse/INFRA-17133
[2] https://issues.apache.org/jira/browse/INFRA-15964
[3] https://issues.apache.org/jira/browse/INFRA-13514
[4] https://issues.apache.org/jira/browse/INFRA-16927
[5] https://issues.apache.org/jira/browse/INFRA-12197
[6] https://issues.apache.org/jira/browse/CASSANDRA-14240
[7] https://developer.github.com/apps/migrating-oauth-apps-to-github-apps/

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 31 2018
  • Taking votes
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    27 Mar 23:08

    This is an issue for our organization as well.  We want to trigger CircleCI builds on GitHub pushes (and PRs) without giving write access to our repositories.