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.

Sign up for GitHub

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

Jump to bottom

getBuildChanges API is Capped to 50 Commits from Azure DevOps #272

Open
jbristowe opened this issue Sep 20, 2022 · 0 comments
Open

getBuildChanges API is Capped to 50 Commits from Azure DevOps #272

jbristowe opened this issue Sep 20, 2022 · 0 comments
Labels
kind/bug

Comments

@jbristowe
Copy link
Contributor

It has been observed that the API call, getBuildChanges appears to cap the number of commits returns by the Azure DevOps API to 50 entries. This means that commit data for a release/deployment may be missing from the associated build information.

This issue needs to be investigated and verified.

Related: 200 commits only from build changes API
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jbristowe