Slash your deployment times with incremental deployments
Blog post from Humanitec
Humanitec has introduced incremental deployments to enhance deployment efficiency by updating only the resources that have changed or previously failed, rather than re-provisioning all resources in an environment, which was the default method before. This new approach allows for substantial reduction in deployment times, potentially by 75% or more, depending on the setup and provisioning mechanisms used. Incremental deployments are optional and can be activated on a per-deployment basis by adding the "--mode incremental" flag to the deployment call. However, limitations exist, such as the lack of drift detection for skipped resources and the necessity to manually handle secret version updates to ensure resources are re-provisioned when needed. Users are encouraged to balance speed and risk by testing both incremental and full deployments, considering the specific needs and configurations of their systems.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 3 | 1,658 | 258 | 90 | +29% |
| Kubernetes | 1 | 2,168 | 322 | 107 | +10% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.