Azure DevOps (formerly Visual Studio Team Services)

Announcement: Last fall, we migrated this forum to Developer Community to provide you one convenient and responsive system for all feedback. As the final step in the migration, this forum will be closed off completely on June 1st, 2019. We encourage you to visit Azure DevOps Developer Community where you can now suggest new ideas, browse and vote on existing ideas, and engage with Azure DevOps teams

We’d like your suggestions and ideas to help us continuously improve future releases of Azure DevOps and Team Foundation Server (TFS), so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

We look forward to hearing from you!
- The VSTS Team

How can we improve Azure DevOps?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Improve hosted build agent performance with build caches

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365799/improve-hosted-build-agent-performance-with-build.html
    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 asp.net 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
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    56 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  2. Increase the hosted build agent size limit from 10GB

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365616/increase-the-hosted-build-agent-size-limit-from-10.html
    Currently you can only use the hosted build if your build + repository is less than 10GB. Even with a shallow fetch our repository is near 10GB and then we run into issues while building.

    62 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  3. Publishing Build Artifacts is way too slow

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/365656/publishing-build-artifacts-is-way-too-slow.html
    We are using the Publish Build Artifacts task and it is incredibly slow. We'd like to see this get faster.

    https://www.visualstudio.com/en-us/docs/build/steps/utility/publish-build-artifacts

    59 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  4. Please support CI/CD for .usqlproj

    Please support CI/CD for .usqlproj (Azure Data Lake Analytics project) on a VSTS hosted agent.

    Make .usqlproj buildable and deployable - that's easy to identify errors at build time.

    3 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →
  5. Simpler YML file format documentation

    As part of delivering:https://visualstudio.uservoice.com/forums/330519-visual-studio-team-services/suggestions/17371657-build-definitions-as-code

    The discovery of YML features would be greatly improved by providing a “hamburger with the lot” style yml file, showing all major features in context. A great example of this is how Appveyor presents their yml reference:

    https://www.appveyor.com/docs/appveyor-yml/

    I think a lot of people coming from Travis, appveyor or gitlab are going to go ‘yml first’, and are going to need structurally correct examples to help make that first experience ‘delightful’, as they say.

    1 vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CI (Build)  ·  Flag idea as inappropriate…  ·  Admin →

Azure DevOps (formerly Visual Studio Team Services)

Feedback and Knowledge Base