Azure DevOps build pipeline stuck at loading build history

590 Views Asked by At

Azure DevOps build pipelines stuck at loading the build history, It is happening for few pipelines but rest are fine. When I recreate these pipelines with same templates, those all are working fine and showing the build history, but am worrying why particular these pipelines are not showing. We are using the other git connection for these pipelines. Is it because of too long build history. I use the filters to load the history. Its working fine with feature and other branches and showing the history but not for Main branch. Am confusing why it is not loading the build history for the Main branch. How can I sort out this issue. Please someone help me on this. Am sharing the pics of above issue with and without filters. Thank you.

Without filters continuous loading page enter image description here

child branch build history with filters enter image description here

Main branch continuous loading page with filters enter image description here

Picture for retention policies enter image description here

Pipeline retention policy enter image description here

1

There are 1 best solutions below

10
Kim Xu-MSFT On

Yes, it is caused by long build history on the main branch. Since it shows correctly when recreating these pipelines with same templates.

In Azure DevOps, you could use Retention policies to set how long to keep runs, releases, and tests stored in the system. To save storage space, you could delete older runs, tests, and releases.

enter image description here

Pipelines - List API is supported to get all the history runs from a specific pipeline.

enter image description here

Update 1

I have checked the official doc for Azure DevOps Server.

This API is supported via TFS2020.

enter image description here

But not supported via TFS2019.

enter image description here

For TFS and API version mapping, you could check this link.

For Version 5.0 supported API. I could see there is API to get the builds by build ID, but not pipeline.

enter image description here

Update 2

You could check why this run is being retained on the pipeline summary page.

enter image description here

enter image description here

For GitHub repo, as addressed here,

All other Git repositories: Azure Pipelines retains the configured number of latest runs for the whole pipeline.

There are other related settings could affect the build pipeline retention policy, for example, if the build pipeline provides an Artifact.

enter image description here