Menu
type 'Microsoft-Hosted Private'
Getting this error running a pipeline on a new account so there're enough credits/limits It has been stuck for close 20+ hours now, have tried to recreate projects/subscriptions/pipelines and what not but no dice
There are similar questions on vscommunity but no answers so hoping someone has insights here
Turns out this is a "feature" implemented recently, closing this question will leave it here till it's deleted or whatever in case someone stumbles upon this same error
https://devblogs.microsoft.com/devops/change-in-azure-pipelines-grant-for-private-projects/
393
In Azure Pipelines, you can run parallel jobs on Microsoft-hosted infrastructure or your own (self-hosted) infrastructure. Each parallel job allows you to run a single job at a time in your organization. You do not need to pay for parallel jobs if you are using an on-premises server.
Sign-in to your Azure DevOps organization and go to your project. Go to Pipelines, and then select New pipeline. Do the steps of the wizard by first selecting GitHub as the location of your source code. You might be redirected to GitHub to sign in.
Edit the pipeline you want to modify. On the Options tab, there is an option Build job timeout in minutes, which you can set the Build job timeout, the default value is 60 minutes. This timeout are including all tasks in your build pipeline rather than a particular job, if one of your build step out of time.
Azure DevOps (ADO) is not going away anytime soon and will get plenty of love. It is one of the undervalued things about Microsoft – its long-term commitment to the lifecycle of its software and providing new features and support for its customers.
If you have started working on exploring Azure DevOps pipelines recently, then you would have faced an issue with the message This agent request is not running because you have reached the maximum number of requests that can run for parallelism type ‘Microsoft-Hosted Private’. Current position in queue: 1 as shown in the below screenshot
There is a maximum limit of 25 parallel jobs for Microsoft-hosted agents. Starting with Azure DevOps Server 2019, you do not have to pay for self-hosted concurrent jobs in releases. You are only limited by the number of agents that you have. Learn how to estimate how many parallel jobs you need and buy more parallel jobs for your organization.
If you would like to build your pipelines (for automating any of your tasks) using Azure DevOps, then you need Compute power in order to execute / run the pipeline. By default, Microsoft (used to) provides Microsoft hosted Virtual Machines called Azure Pipelines.
You can use a parallel job in Azure Pipelines to run a single job at a time in your organization. In Azure Pipelines, you can run parallel jobs on Microsoft-hosted infrastructure or on your own (self-hosted) infrastructure. If you want to run your jobs on machines that Microsoft manages, use Microsoft-hosted parallel jobs.
The root cause of the stuck issue is that the pipeline microsoft-hosted agent for public and private projects in the new organization has been restricted in the latest update.
For more detailed info, you could refer to these two docs: Private Project Pipelines, Public Project Pipelines.
In Release 183, the reasons for adding restrictions are as follows:
Over the past few months, the situation has gotten substantially worse, with a high percentage of new public projects in Azure DevOps being used for crypto mining and other activities we classify as abusive. In addition to taking an increasing amount of energy from the team, this puts our hosted agent pools under stress and degrades the experience of all our users – both open-source and paid.
Private Project:
You could send email to [email protected] in order to get your free tier.
Public Project:
You could send email to [email protected] in order to get your free tier.
196
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
