feat: add Azure DevOps enterprise integration support #11667
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zerofltexx
force-pushed
the
feat/azure-devops-support-enterprise
branch
25 times, most recently
from
17058e1 to
14b9c54
Compare
4 tasks
zerofltexx
force-pushed
the
feat/azure-devops-support-enterprise
branch
6 times, most recently
from
95fd5c4 to
e90b397
Compare
neubig
reviewed
Nov 22, 2025
Contributor
neubig
left a comment
neubig
left a comment
There was a problem hiding this comment.
I'm happy to take a look at this when merge conflicts are resolved and tests are passing, please re-request review then!
zerofltexx
pushed a commit
to zerofltexx/OpenHands
that referenced
this pull request
Nov 22, 2025
Resolved merge conflicts between enterprise Azure DevOps integration (PR OpenHands#11667) and the base Azure DevOps integration that was merged into main (PR OpenHands#11243). Key conflict resolutions: - Kept X-VSS-UserData header parsing for subject ID extraction (needed for work item assignment matching in enterprise webhooks) - Kept Markdown to HTML conversion for Azure DevOps comment formatting - Kept get_work_item method (used by enterprise webhook code) - Kept selected_branch handling for linked development branches - Kept users/openhands/{id} branch naming format - Added add_work_item_reaction method from main branch All enterprise-specific features have been preserved while incorporating updates from the main branch. Co-authored-by: openhands <[email protected]>
zerofltexx
pushed a commit
to zerofltexx/OpenHands
that referenced
this pull request
Nov 22, 2025
Resolved merge conflicts between enterprise Azure DevOps integration (PR OpenHands#11667) and the base Azure DevOps integration that was merged into main (PR OpenHands#11243). Key conflict resolutions: - Kept X-VSS-UserData header parsing for subject ID extraction (needed for work item assignment matching in enterprise webhooks) - Kept Markdown to HTML conversion for Azure DevOps comment formatting - Kept get_work_item method (used by enterprise webhook code) - Kept selected_branch handling for linked development branches - Kept users/openhands/{id} branch naming format - Added add_work_item_reaction method from main branch All enterprise-specific features have been preserved while incorporating updates from the main branch. Co-authored-by: openhands <[email protected]>
zerofltexx
force-pushed
the
feat/azure-devops-support-enterprise
branch
3 times, most recently
from
f6bcc5b to
acfb349
Compare
zerofltexx
force-pushed
the
feat/azure-devops-support-enterprise
branch
from
87c19b8 to
9c09ccd
Compare
zerofltexx
force-pushed
the
feat/azure-devops-support-enterprise
branch
3 times, most recently
from
7647ce1 to
38170e5
Compare
Contributor
Author
|
Fix: Mainly to rename Azure DevOps webhook table migration (083 -> 084). New migration file took over 83 & merged to main before this one.
The failed test is due to this |
zerofltexx
force-pushed
the
feat/azure-devops-support-enterprise
branch
8 times, most recently
from
4f13bfd to
1f25ce7
Compare
This commit adds enterprise-grade Azure DevOps support with webhook-based automation and service principal authentication for multi-tenant SaaS deployments. Key changes: - Implemented webhook event processing for work items and pull requests - Added service principal authentication for automated operations - Implemented Azure DevOps manager for handling webhook events - Added work item and PR comment support with @mention detection - Created callback processor for asynchronous webhook responses - Added webhook registration and management endpoints - Implemented Azure DevOps user enrichment and token management - Added database schema for webhook storage - Fixed API response format handling for comments and field values - Removed linter suppressions for cleaner code The implementation enables: - Automated responses to work item assignments and @mentions - Pull request comment handling with inline code review support - Service principal-based API operations for scalability - Multi-organization support with webhook deduplication - Integration with Keycloak for user management - Webhook-driven conversation creation and management
zerofltexx
force-pushed
the
feat/azure-devops-support-enterprise
branch
from
1f25ce7 to
bf7aaa8
Compare
Contributor
|
Hi, just a note, I'll circle back to reviewing this next week after we (hopefully) finish with shipping OpenHands v1 to the OpenHands cloud. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
End-user friendly description
This PR adds enterprise/SaaS support for Azure DevOps integration. It builds on top of /pull/11243 PR by adding SSO authentication, user identity mapping, and webhook security features required for multi-tenant SaaS deployment.
Summary
This PR extends the base Azure DevOps integration PR with enterprise-specific features.
What This PR Adds
azure_devops_id)(organization, subscriptionId, api_key)lookupAzureDevOpsServiceImplwith SaaS-specific featuresPrerequisite
Please follow the README.md in All-Hands-AI/OpenHands-Cloud/pull/238
Azure DevOps (Client side - unfortunately this can't be automated based on my research)
Create an API key. Have this ready for the next step
Create the webhook, since it is at project level, this pair needs to be created in every project. In HTTP headers paste the API key like so:
To-do
Related Issues