Azure Pipeline Caching

LukasB

Hello,

we have Azure pipelines in place for our ci/cd process like it is described here

https://docs.spryker.com/docs/ca/dev/configure-deployment-pipelines/configure-azure-pipelines.html#prerequisites

The execution of the pipeline currently takes quite long (the largest step is the docker/sdk up -t). Does anybody know if it's possible to add the Azure pipeline build in caching system to reduce the image download part, and maybe also the composer part?

profuel

Hi, @LukasB !

I have asked another team, who works with Azure Pipelines as well, whether they have some caching in place.

profuel

So, let's compare numbers - this is how the pipeline looks for them:

Is it much worse for you?

LukasB

Thanks for checking @profuel!

I assume the 'Build images' step (docker/sdk up -t ) is the 'Launch project' step from the documentation. Is that right?

Regarding the numbers, this step takes a lot longer for me:

Is there any way to add caching to this step? The project I'm referring to does not have many changes (quite close to the B2B demo shop) at the moment.

profuel

Sorry, @LukasB , I'm not an expert in Azure pipelines, and so far I haven't heard anything about the caching in pipelines as well.

profuel

Thanks to my colleague, I have some ideas for you:

1. Docker build itself is really fast, like 1 minute. The rest of time is building data based on the configuration you have made.
2. so, review your install scripts for CI pipeline, and make sure you have bare minimum to make it work correctly.

LukasB

Thanks for sharing @profuel! I will try to figure out where the most time is spent.

victor.vanherpt

Hey @LukasB ! I see we're on the same boat regarding Azure pipelines in our projects ;) Maybe we can sync sometime to share ideas regarding our setups (as we share the same infra ;) )

I believe this is not a Spryker specific topic, but a topic for the DevOps team to resolve (or enable us to resolve)

LukasB

Hey @victor.vanherpt!

Sure let's sync and share some ideas :)