 If you want to go towards a stage-free pipeline, or defining stages is completely unnecessary for your use case, in GitLab 14.2, now it's possible to define stage-laced pipelines. And how do we do it? By defining the needs relationship between any job you want, it is possible to create a complete CI-CD pipeline without using stages, including needs in every job will configure the execution order. My name is William, and let's see a stage-less pipeline in action. I have this project that builds a website and deploys it to Kubernetes. Previously, I needed to define different stages for build, test, review, and deploy. In this case, you can see I don't have any stage defined, but I have defined the relationship between these jobs by using needs. For instance, this job needs the Docker image to be built first. In the pipeline editor, I can group by jobs and get a visual representation of them and its dependencies. As we can see here, the pipeline is executing right now. Alright, my stage-less pipeline has finished. I want to check the review app. Let's go back to the Merch Request page and open the website. And here it is. My website has been deployed to my Kubernetes cluster. Great! We were able to create a complete CI-CD pipeline without using any stage. Does this help you in any of your use cases? Stay tuned and let's continue learning at GitLab.