You can go to the Pipelines page in CI Visibility to confirm if your particular pipeline is experiencing high build durations. After pushing new code, you notice that your builds are extremely slow-much slower than normal. Say you’re an engineer at an e-commerce company where one of the checkout services for your primary application is undergoing a major revamp under a tight deadline. Investigate pipeline failures to fix erroneous buildsĪfter you enable the TeamCity integration in CI Visibility, you can use the Pipeline overview page to get a high-level view of the health and performance of your TeamCity build chains, with key metrics such as executions, failure rate, build duration, and more. If you navigate to the Pipelines page, you can see TeamCity pipelines alongside any other providers you may have instrumented with CI Visibility. Once you’ve enabled the integration, data from your TeamCity pipelines will automatically flow into Datadog.
Making data-driven decisions to increase the performance and reliability of your pipelines will help you improve end-user experience by allowing your team to push code releases faster and with fewer errors. This article was originally written by Nicholas Thomson and Kassen Qian of Datadog and published on the Datadog blog.Īs the complexity of modern software development lifecycles increases, it’s important to have a comprehensive monitoring solution for your continuous integration (CI) pipelines so that you can quickly pinpoint and triage issues, especially when you have a large number of pipelines running.ĭatadog now offers deep, end-to-end visibility into your TeamCity builds with the new TeamCity integration for CI Pipeline Visibility, helping you identify bottlenecks in your CI system, track and address performance regressions, and proactively improve the efficiency of your CI system.
0 kommentar(er)
