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

feat: add remote repository support for azure devops #7364

Merged
merged 1 commit into from
Apr 25, 2024

Conversation

mr-ks
Copy link
Contributor

@mr-ks mr-ks commented Apr 23, 2024

Summary

It is now possible to choose remote repositories connected through 'service connections' as a data scope. Tasks in the cicd and code domains are performed based on the visibility of these repositories (public or private).

⚠️ This pull request includes a database migration. The _tool_azuredevops_go_repos is extended with the following columns.

name default value reason
Type TfsGit Indicates the source provider (TfsGit, GitHub, ...), necessary to retrieve the builds from the Azure DevOps API
IsPrivate false Required to build the blueprint, tasks from the domain DOMAIN_TYPE_CODE are excluded for private repositories
ExternalId null Necessary to retrieve the builds from the Azure DevOps API

Does this close any open issues?

Resolves #7307

Screenshots

The Azure DevOps Go plugins now provide additional information about the current processed data scope.

image

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.

It is now possible to choose remote repositories connected through 'service connections' as a data scope. Tasks in the cicd and code domains can be performed based on the visibility of these repositories (public or private).
@klesh klesh merged commit ca89492 into apache:main Apr 25, 2024
11 checks passed
@klesh
Copy link
Contributor

klesh commented Apr 25, 2024

LGTM, Thanks for your contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants