Latency detection in a deployment build pipeline

A method, comprising:

• performing, by one or more computing devices configured to implement an automatic code deployment pipeline system:
• responsive to determining an update to a component of an application to be automatically deployed, via the automatic code deployment pipeline system, to a production execution environment:
• running the application including the updated version of the component at a stage of an automatic code deployment pipeline system providing a portion of a production execution environment that is a less-than-full-production execution environment;
• analyzing:
• latency data for one or more latency metrics for the version of the application that includes the updated component running in the portion of a production execution environment that is a less-than-full-production execution environment relative to latency data for the one or more latency metrics for the application running in an execution environment,
• wherein the one or more latency metrics comprise one or more end-user latency metrics that approximate latency perceivable by an end-user and are based at least in part on a time when a response to the request is ready to send without accounting for transmission time to a device where the latency would be perceived by the end-user;
• determining, based on the analyzing, whether inclusion of the updated component in the application results in a latency regression for the application;
• and
• halting, responsive to determining, based on the analysis of the latency data, that inclusion of the updated component in the application results in a latency regression for the application, the automated deployment for the updated application;
• or
• continuing, responsive to determining, based on the analysis of the latency data, that inclusion of the updated component in the application does not result in the latency regression for the application, the automated deployment for the updated application.

One or more non-transitory computer-readable media storing program instructions executable on or across one or more processors to implement an automatic code deployment pipeline configured to:

• responsive to determination of an update to a component of an application to be automatically deployed to a production execution environment:
• run the application including the updated version of the component at a stage of an automatic code deployment pipeline system providing a portion of a production execution environment that is a less-than-full-production execution environment;
• determine, based on analysis of latency data for one or more latency metrics for the version of the application that includes the updated component running in the portion of a production execution environment that is a less-than-full-production execution environment relative to latency data for the one or more latency metrics for the application running in an execution environment, whether inclusion of the updated component in the application results in a latency regression for the application, wherein the one or more latency metrics comprise one or more end-user latency metrics that approximate latency perceivable by an end-user and are based at least in part on a time when a response to the request is ready to send without accounting for transmission time to a device where the latency would be perceived by the end-user;
• and
• halt, responsive to determining, based on the analysis of the latency data, that inclusion of the updated component in the application results in a latency regression for the application, the automated deployment for the updated application;
• or
• continue, responsive to determining, based on the analysis of the latency data, that inclusion of the updated component in the application does not result in the latency regression for the application, the automated deployment for the updated application.