-
Notifications
You must be signed in to change notification settings - Fork 730
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
Azure Pipelines: Give contributors access to build log #71
Comments
As Azure Pipelines is meant to be a stopgap solution, the stopgap solution you propose (adding active contributors manually) to this limitation seems the best approach for the time being. Maybe with the GitHub acquisition, Azure Pipelines will gain the ability to do oauth with GitHub, allowing team access permissions (just like bubble.servers.lowrisc.org does for the docs). |
As expected after the GitHub acquisition, things are getting better integrated. Soon a GitHub account will allow users to log in to Azure, as announced today in https://azure.microsoft.com/en-gb/blog/accelerating-devops-with-github-and-azure/
It's likely that GitHub group support comes soon as well. So I'm not planning to do anything on our side for now. |
Scrubbing stale issues. @imphil , have they enabled this capability yet? |
no |
https://dev.azure.com/lowrisc/opentitan is now public, all build results are visible there. |
Currently this repository and the Azure Pipelines builds are "private", which means failing PRs only show a single line of (rather useless) build output. Since Azure Pipelines doesn't support syncing the team permissions from GitHub we need to manually add users with write permissions to stwg-base also to Azure Pipelines.
For now, if you want to see the full CI build log, please drop me a mail with your Microsoft or Skype account name. I'll add you to the right group.
If we want to go fancy (and have time), we can explore a couple more options:
Or we could just wait until we go public or choose another CI solution and the permission problems vanish.
The text was updated successfully, but these errors were encountered: