How can we improve Azure DevOps?

Improve hosted build agent performance with build caches

This suggestion is migrated to Developer Community. Please use below link to view the current status.
Consider options to reduce build time of hosted build agent significantly. I don't have problem paying for improved performance if there were such option.

For example dotnet restore build task takes 95 seconds for simple core 2 app in each build. Packages could be cached.

Agent initialization takes 39 seconds. Agent could be initialized in advance, why not?

357 votes
Sign in
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    liero shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      • Hugo Veillette commented  ·   ·  Flag as inappropriate

        Hi, could you please follow up on the ETA of the feature? We are passed 12 months last update.

        Thank you.

      • Oliver commented  ·   ·  Flag as inappropriate

        any update?? you say your working on it back in feb its now nearly 1 year later?

      • phil-lgr commented  ·   ·  Flag as inappropriate

        I second this, most CI service have caching feature now

        in circle-ci you can do

        - save_cache:
        key: cache-{{ checksum "package-lock.json" }}
        - node_modules

      • Joseph Priolo commented  ·   ·  Flag as inappropriate

        One solution is build your own 'build agents'. Install what you need. I agree though, these hosted agents are dirt slow.

      • Mike Brosnan commented  ·   ·  Flag as inappropriate

        There are many features in Artifactory around artefact and dependency management, are you working on a MVP for dependency management/ proxying maven repos, what is the roadmap?

      • Andrew Stoker commented  ·   ·  Flag as inappropriate

        Adding my voice here. Building locally (when we have a cache) takes about 30 seconds. Without the cache, we're downloading a lot and our build times take upwards of 5 minutes. Having a cache is extremely important to our build process.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Any update on this? Downloading a 2.5GB SDK we need every time we build really slows our builds.

      • Dennis Hsu commented  ·   ·  Flag as inappropriate

        Can we update the NodeJS version on hosted agent?

        I used Node.JS Tool installer to install LTS 8.12.0 and it reduced our NPM install step by 32 seconds, but the install of 8.12.0 took 39 seconds, so no overall gain.

        But can Azure DevOps install the latest Node.JS module on hosted agent? or allow user select which version of NodeJS to use?


      • AJ Soto commented  ·   ·  Flag as inappropriate

        Does anyone know if by using Azure Artifacts - and setting up a feed that allows packages from public sources (like nuget), will make the builds from a hosted agent any faster since if would be getting the packages from the Azure Artifacts feed (after of course the initial download/restore of all the nuget packages) instead of from NuGet?

      • Aaron Aichlmayr commented  ·   ·  Flag as inappropriate

        Any news on this one? Even if this would be an azure disk resource we could have mounted it would solve the need

      • liero commented  ·   ·  Flag as inappropriate

        @Admin, @VSTS Team:
        would you please update?
        Is it already "being tracked in the right places internally"?
        Also, I'm very curious, what could be causing @Michael Bruyninckx's problem: "Every NPM interaction (like "npm --version" or "npm set progress=false") takes about 3 minutes. Every NPM step we add, adds 15 minutes extra buildtime". It does not seem like cache problem

      ← Previous 1 3

      Feedback and Knowledge Base