New Feature: Deployment Pipeline
What is Qovery's Deployment Pipeline Feature?
A Deployment Pipeline consists of multiple stages, each with an assigned execution order within the pipeline. When you trigger the deployment of an environment, Qovery executes this pipeline to deploy every service defined within your environment. Each service belongs to one (and only one) Deployment Stage, allowing you to define at which moment of the deployment pipeline a service should be deployed and thus respect any service inter-dependency.
Why does it matter?
The Deployment Pipeline feature enables you to configure each stage and its order of execution, allowing for greater control over your deployment process. With this feature, you can ensure that services are deployed in the correct order to meet any dependencies between them. This is especially important when dealing with complex applications that have multiple services with varying dependencies.
For instance, you might need to guarantee that your Databases start before your Backend, your API Gateway starts after your Backend and your Frontends after your API Gateway.
Qovery's Deployment Pipeline feature allows for parallel deployment, which can significantly reduce the time it takes to deploy your services. By executing multiple steps in parallel, you can speed up the deployment process and reduce the risk of downtime during deployment.
How does it work?
Each stage in the deployment pipeline consists of multiple steps that can be executed in parallel. The steps can include building and deploying your services. Qovery's Deployment Pipeline feature allows you to configure each step and its order of execution within a stage, ensuring that everything runs smoothly during deployment.
Additionally, Qovery's Deployment Pipeline feature offers the flexibility to configure certain actions to be performed at specific stages of the pipeline. For example, you can seed your database after it has started but before the application starts, or perform a database backup when the environment is deleted. It's up to you to do whatever you need within your deployment pipeline.
What's next?
Qovery's Deployment Pipeline feature is just the beginning. We have a few enhancements planned that we're excited to share with you:
- A dedicated view to see the deployment pipeline and where it has failed, along with an enhanced view of the deployment logs to better see where the deployment process has failed.
- Retrigger a complete stage instead of the complete pipeline or a step.
- Decouple Build and Deployment phase: Decoupling the Build and Deployment phase will be possible to speed up the deployment process depending on the user use case. For instance, sometimes, the build can be done ahead of all deployments, but the deployment only must be ordered.
We're always open to feedback and suggestions, and we invite you to share your thoughts on our public roadmap.
Conclusion
Qovery's Deployment Pipeline feature is a big milestone for us, and we're excited to share it with our users. By enabling greater control over service deployment order and offering the flexibility to configure certain actions at specific stages of the pipeline, we're confident that this feature will make the deployment process even faster and smoother. We can't wait to see what you'll build with it!
Resources
.svg)
.svg)
.svg)
Suggested articles
Qovery is officially SOC 2 Type II compliant with an Unqualified Opinion. Get the highest assurance of continuously verified security controls for enterprise-grade application deployments and simplify due diligence.
Following the launch of Qovery Observe, we’re progressively adding new capabilities to help you better monitor, debug, and understand your applications. Today, we’re excited to announce a major improvement to the Logs experience: you can now search and filter directly within your application logs.
Compare the top 10 AWS ECS alternatives, including Qovery, Docker, EKS, and GKE. Find the best solution to simplify Kubernetes, automate DevOps, and achieve multi-cloud container deployment.
Because various organizations need cloud application and service management that offers different levels of simplicity, cost-effectiveness, or feature sets than OpenShift, this article will review its top alternatives to help readers make an informed decision aligned with their specific infrastructure needs.
Running GPU workloads on EKS has never been easy, until now. With Qovery’s latest update, you can enable GPU nodes, configure GPU access, and optimize costs automatically, all without writing a single line of YAML or touching Helm charts. Qovery now handles everything behind the scenes so you can focus entirely on your applications.
Master Kubernetes deployment strategies: Rolling Update, Recreate, Blue/Green, and Canary. Learn the pros, cons, and use cases to choose the right strategy based on your uptime, risk tolerance, and resources. Simplify complex rollouts with automation.
.webp)