I created Pull Request which triggers the build and the build was successful, but after some time my build status changed to "build expired" so to finish pull request I need to trigger it one more time. So the question is: Why has this happened and how to avoid build to be expired?
相关问题
- Docker task in Azure devops won't accept "$(pw
- Authentication Failure using Git-LFS Azure DevOps
- Authentication Failure using Git-LFS Azure DevOps
- Getting error: File extension specified '.webt
- Using TFS command line tf.exe how can I copy a rep
相关文章
- Build errors of missing packages in Visual Studio
- Is it possible to do a “destroy history” in TFS?
- VSTS continuous integration triggers not working
- How do I make a TeamCity build appear in the TFS B
- TFS vs. JIRA/Bamboo/SVN [closed]
- Why doesn't my .tfignore file ignore my packag
- Is it possible to create a docker container from T
- How to Move TFS 2010 Build Definition between Proj
So the "build expired" is a feature of branch policies. Set a build expiration to make sure that updates to your protected branch don't break changes in open pull requests.
Always require a new build: This option sets the build policy status in a pull request to failed when the protected branch is updated. You must requeue a build to refresh the build status. This setting ensures that the changes in pull requests build successfully even as the protected branch changes. This option is best for teams that have important branches with a lower volume of changes. Teams working in busy development branches may find it disruptive to wait for a build to complete every time the protected branch is updated.
Require a new build if older than...hours: This option expires the current policy status when the protected branch updates if the passing build is older than the threshold entered. This option is a compromise between always requiring a build when the protected branch updates and never requiring one. This choice is excellent for reducing the number of builds when your protected branch has frequent updates.
Don't require a new build: Updates to the protected branch do not change the policy status. This reduces the number of builds for your branch, but can cause problems when closing pull requests that haven't been updated recently. Details here
On the overview of the push request, next to "Build Expired" - click on the ellipses (3 dots to the right) and select "Queue Build". If it fails, pull master, merge it into your branch and re-push.