-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add Azure DevOps integration #20202
Add Azure DevOps integration #20202
Conversation
components/dashboard/src/data/auth-providers/create-user-auth-provider-mutation.ts
Show resolved
Hide resolved
Awesome work @mustard-mh ! 🧡 |
components/dashboard/src/data/auth-providers/update-org-auth-provider-mutation.ts
Outdated
Show resolved
Hide resolved
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
b70b83c
to
f33d5a3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
leaving some initial comments, will do another round before approving
components/dashboard/src/data/auth-providers/update-org-auth-provider-mutation.ts
Outdated
Show resolved
Hide resolved
components/dashboard/src/data/auth-providers/update-user-auth-provider-mutation.ts
Outdated
Show resolved
Hide resolved
found = true; | ||
isPrivateRepo = true; | ||
writeAccessToRepo = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could be useful to add a comment about why we can make these assumptions. I know that it has to be private, but am not for instance sure about the write access one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no API to check if user has write permission on a repo. We assume user has write permission so that we don't show git permission missing on user push.
If write permission is actually missed, user can find it out from git commands error output
} | ||
|
||
async getUserRepos(user: User): Promise<RepositoryInfo[]> { | ||
// FIXME(janx): Not implemented yet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: poor @jankeromnes!
// FIXME(janx): Not implemented yet | |
// todo(hw): Not implemented yet |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😆
return result | ||
.slice(1) | ||
.map((c) => c.commitId) | ||
.filter((c) => !!c) as string[]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: we could get rid of the type assertion by upgrading typescript
components/server/src/azure-devops/azure-context-parser.spec.ts
Outdated
Show resolved
Hide resolved
Co-authored-by: Filip Troníček <[email protected]>
@mustard-mh I wonder if there's something easy we can do on the integrations page WRT the Azure DevOps endpoint: I am not sure if we are at all compatible with DevOps server, but depending on that it'd be great to either nudge / restrict the endpoint to |
- dashboard provider type update - doc for checkWriteAccess - Requirement.DEFAULT
This reverts commit 189c431.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's get this Friday evening shipped 🚀
Incredible work, Huiwen!
/unhold |
Description
Related Issue(s)
Fixes ENT-552, ENT-780
How to test
It can setup an Azure DevOps integration
‼️ there should have only one DevOps integration in an installation because providers are uniq by host. There's only one org in Gitpod Enterprise, so it should be safe there. In preview env, it's working because of
utils.ts
changesTest with Git Integration
Documentation
Preview status
Gitpod was successfully deployed to your preview environment.
Build Options
Build
Run the build with werft instead of GHA
Run Leeway with
--dont-test
Publish
Installer
Add desired feature flags to the end of the line above, space separated
Preview Environment / Integration Tests
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Saves cost. Untick this only if you're really sure you need a non-preemtible machine.
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh
. If enabled,with-preview
andwith-large-vm
will be enabled./hold