feat: add remote repository support for azure devops #7364
Merged
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.
Summary
It is now possible to choose remote repositories connected through 'service connections' as a data scope. Tasks in the
cicd
andcode
domains are performed based on the visibility of these repositories (public or private)._tool_azuredevops_go_repos
is extended with the following columns.builds
from the Azure DevOps APIDOMAIN_TYPE_CODE
are excluded for private repositoriesbuilds
from the Azure DevOps APIDoes this close any open issues?
Resolves #7307
Screenshots
The Azure DevOps Go plugins now provide additional information about the current processed data scope.
Other Information
listAzuredevopsRemoteScopes
has been refactored to retrieve data scopes in parallel, reducing the user's waiting time.Disabled
AzureDevOps repositories are not included in the list.