Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: update Azure to allow external access #74

Closed
rebello95 opened this issue Jun 12, 2019 · 2 comments
Closed

ci: update Azure to allow external access #74

rebello95 opened this issue Jun 12, 2019 · 2 comments
Assignees
Labels
Milestone

Comments

@rebello95
Copy link
Contributor

Right now the Azure organization used for CI doesn't allow contributors to this repo to see details on CI jobs. We'll need to update these policies to allow others to see this information.

@junr03 feel free to add more details here.

@rebello95 rebello95 added the ci label Jun 12, 2019
@rebello95 rebello95 added this to the v0.1 "Antipasto" milestone Jun 12, 2019
@junr03
Copy link
Member

junr03 commented Jun 12, 2019

The way that I set this up yesterday is not the long term solution -- yesterday I created the azure pipelines for this repo under an island project owned by me, not the lyft github org. This unblocked us and got CI pipelines running for the repo, but organizationally the pipelines are not running where they should.

I am meeting friday with @asottile to come up with a sustainable and secure place for the pipelines. Whether that is on their own azure project, or on a project owned by Lyft.

@junr03 junr03 modified the milestones: v0.1 "Antipasto", v0.2 "Primo" Jun 17, 2019
@junr03
Copy link
Member

junr03 commented Jul 8, 2019

This is done. I have created an envoy-mobile org that has a public project for this repo. All contributors should be able to see jobs. All maintainers have access to re-kick jobs.

@junr03 junr03 closed this as completed Jul 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants