Kentico too big for azure dev ops build pipeline

Kàren Vaganyan asked on October 28, 2018 20:42

I should start with saying that this is my first time really using Azure Dev Ops and setting up pipelines, so I apologize if I don’t understand things right away and seem a little slow haha

I have a large Kentico CMS project (It’s a .NET C# Website project) that I’m trying to setup a build pipeline for but unfortunately because it is so big, the 30 minute timeout always cancels the build process and I’m not too sure what to do to speed it up.

Below are my available pools to choose from. I don’t think we have any self hosted pools at the moment.

Image Text

This is all for my job. I unfortunately don’t have full access to our Azure Dev Ops or our Azure Portal but there are some settings and configurations that I think I should be able to do. If there are some settings or adjustments that I don’t have access to, I can pass that information along to our IT and Platform Services department.

Please let me know what other information I should provide.

Correct Answer

Juraj Ondrus answered on October 29, 2018 09:29

This is a duplicate question, already asked and answered on StackOverflow.

0 votesVote for this answer Unmark Correct answer

Recent Answers

Peter Mogilnitski answered on October 29, 2018 13:23

You have to create your own pool of agents and do not depend on anyone. We have an Azure VM with a pool of 4 agents (It can be your server on premise). You might want to build other solution (APIs)a the same time. You need to have a few agent in the pool. If you have one agent and build is long it means all other builds will wait for the agent to be free. For CI/CD solution

With a shared agent you not limited only with time, but I believe with the resources as well (CPU and memory). On top of that you might wait for a free agent. If you get your own build server it should be fairy fast. In our kenitco pipeline most of time is taken by javascript bundles, not the Kentico.

0 votesVote for this answer Mark as a Correct answer