Keep your Laravel CI pipeline running fast

CI pipelines tend to get slower over time, the more we add to them, and the bigger our project grows. Keeping an eye on this is important.

Joel Clermont
Joel Clermont

Continuous integration pipelines are a vital part of our software development process. It's a great sanity check before new code is reviewed by another developer, and gives us extra confidence shipping into production.

But over time, these pipelines tend to accumulate more and more complexity. Along with that complexity, comes a longer runtime. Not only does this slow down the review and release process, but it can begin to incur a cost, depending on how your provider is set up.

What started as a quick 2 - 3 minute pipeline can be 5 - 10 minutes before you know it. And because it tends to slow down gradually, you don't always even notice it.

Why am I even mentioning this? It's too easy to become numb to pain in our projects, especially if the pain grows slowly over time. So stay tuned for some upcoming tips on how to keep your Laravel CI pipeline running fast.

In the meantime, hit reply and let me know how long your CI pipeline takes to run. I'm curious!

Here to help,


P.S. We all get stuck sometimes! Need a quick pairing session with a Laravel expert to get unstuck?

Toss a coin in the jar if you found this helpful.
Want a tip like this in your inbox every weekday? Sign up below 👇🏼

Level up your Laravel skills!

Each 2-minute email has real-world advice you can use.