Caching of composer build if nothing has changed between deployments

[jamesmacwhite]

I don't know how feasible this is given the serverless design, but being hosted on similar ephemeral hosting environments like Fortrabbit, using an external CI like Buddy, we could cache the composer deployment step if the composer.lock hadn't changed between deployments. and only when the composer.lock was changed, would the composer build be rebuilt This reduced the deployment time when there were no composer changes, given the composer build was just pulled from the cache on these runs.

The average the build time of the project we are testing is around 5-8 minutes, reviewing the completed build logs, on average 40 seconds is down to the composer build step.

This might not be possible given Fortrabbit isn't serverless and you have an SSH deploy service, which you don't have with Craft Cloud but just opening a discussion as an area for consideration or thoughts.

[timkelty]

@jamesmacwhite we've already been exploring this, along with other improvements to deployment speed. We will keep you updated!