I am trying to deploy a new project through Azure DevOpsPipelines and it shows is as queued for an hour (normally it starts right away or within minutes).
It also says "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"
I have also tried to run a pipeline for one of my existing projects and it has the same issue. Last time I successfully deployed for this projects 8 days ago.
I have seen that they have introduced new rules for free grants for Azure Pipelines for new organizations. I was wondering if these rules are applied to all organizations (including old ones)?
I have sent the email as they requested I am just wondering if they have just taken the free access to Azure pipelines from everyone?
I am also quite new to Azure DevOps so I am wondering if this is a regular thing that Azure services just stop working?
thanks everyone!
Update:
here is my parallel jobs screenshot
Update:
my Azure Pipelines
I was wondering if these rules are applied to all organizations
(including old ones)?
This change only impacts new organizations. It doesn't apply to existing projects or organizations. This does not change the amount of free grant you can get. It only adds an extra step to get that free grant.
I have sent the email as they requested I am just wondering if they
have just taken the free access to Azure pipelines from everyone?
It may take some days to process your requests, please wait patiently.
I am wondering if this is a regular thing that Azure services just
stop working?
Azure Pipelines has been offering free CI/CD to public and private projects for several years. Because this amounts to giving away free compute, it has always been a target for abuse – especially crypto mining. Minimizing this abuse has always taken energy from the team. Over the past few months, the situation has gotten substantially worse, with a high percentage of new projects in Azure DevOps being used for crypto mining and other activities we classify as abusive. Several service incidents over the past month have been caused by this abuse resulting in long wait times for existing customers.
To address this situation, we've added an extra step for new organizations in Azure DevOps to get their free grant.
Please refer to this release notes.
As a temporary alternative, you can install and use self-hosted agents. Please refer to this document.
Related
As an MSP, we manage multiple customer subscriptions through Azure Lighthouse.
Historically we've used a single Automation Account per subscription to contain solutions such as runbooks related to the Start/Stop v1 solution, Automation-based Update Management, Inventory, and Change Tracking. This Automation Account is also linked to a single Log Analytics workspace per subscription.
We've since deployed Start/Stop v2, which uses LogicApps and Azure Functions. We now have a requirement to, as part of stopping and starting some VMs, stop and start some services on the machines itself. I plan on doing this through (PowerShell) Azure Automation Runbooks, which would only stop a VM if the runbook has successfully stopped a service on it.
My question relates to whether a single monolithic Automation Account is the way to go, or whether there are any considerations to be taken if we were to implement multiple Automation Accounts.
(I've noticed Best practice to deploy Azure Automation Account Runbooks, but that's over a year ago. Things might have changed in the mean time)
The best practice related question which you have mentioned still holds good i.e., 2 major attributes to consider are pricing and logical resource allocation. One other attribute to keep in mind while deciding whether to go with single or multiple automation accounts is the limits i.e., if you go with single automation account then does the traffic in your environment or the activities that your automation account does reach the limits mentioned here? If yes, then go for multiple automation accounts approach.
I am trying to implement CI/CD for my private project on Azure. I also have upgraded my subscription to "pay as you go". When I try to save and queue my pipeline, I get the error
##[error]No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request.
Since I already can see 1 self hosted free parallel job(0 MS hosted parallel jobs) why can't they be used? Is there anything I am missing. Although I have already raised a request for parallelism request, is it really required?
This was introduced because they were having issues with some user(s) creating multiple free accounts and effectively taking advantage of the free offer or using it in a way for which it was not intended. You will be able to use a free agent once your request gets processed.
If you want to start using pipelines immediately you can purchase a paid agent, go to Organization Settings, Parallel Jobs and at the top under Private Projects click Purchase parallel jobs. On the next screen put a 1 (or more) in the top right hand box:
Now scroll to the bottom and click Save and you should be good to go.
I am new to Azure and I would like to set up a app service along with a pipeline on devops for continious integration so I decided to try it out with the free plan.
I am trying to set up a pipeline on Azure DevOps with a repository from GitHub and I haven't changed anything in the azure-pipelines.yml so I can test it out if it works. When I run the pipeline and check the default jobs, they are in queue all the time and when I view the messages in the console it says the following:
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
I have tried Googling around but haven't found anything useful yet except that you have to send an email to a specific address (azpipelines-freetier#microsoft.com). Now I have done this, but haven't received any answer yet. Is this the correct solution or am I doing something wrong?
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 azpipelines-freetier#microsoft.com in order to get your free tier.
Your name
Name of the Azure DevOps organization
Public Project:
You could send email to azpipelines-ossgrant#microsoft.com in order to get your free tier.
Your name
Azure DevOps organization for which you are requesting the free grant
Links to the repositories that you plan to build
Brief description of your project
Since you have sent the email, you could wait for the response and get your free tier.
There has been a previous question on this and the accepted answer was Azure Elastic Job agent. The problem I have is that the feature is in preview and it still lacks a lot of functionality like diagnostics and alerting. I also find it to be very unreliable as job get randomly cancelled because of service restarts.
Azure Automation Accounts also works, but it only has a execution/running time of 3 hours. So if your maintenance takes more than 3 hours, this is not an option.
I have previously developed my own application for doing this, but the maintenance and management of this can become a headache.
Another alternative could be to just leverage Azure Data Factory perhaps, but this is a route I have not yet followed.
So what are people actually using to do long running maintenance against Azure SQL Databases that has enough diagnostic information in case something goes wrong and has at least some level of alerting?
PS: The database I need to do maintenance on is not small.
I am new at working with Microsoft Azure and I am trying to open a Notebook from the Azure Machine learning studio.
Every time I try to create a new compute it says Creation failed so I cannot work. My region is francecentral and I have tried different Virtual Machine size
Your reason might be explained here:
As demand continues to grow, if we are faced with any capacity
constraints in any region during this time, we have established clear
criteria for the priority of new cloud capacity. Top priority will be
going to first responders, health and emergency management services,
critical government infrastructure organizational use, and ensuring
remote workers stay up and running with the core functionality of
Teams.
If you qualify for this category, you should reach out to Azure Support or your Microsoft representative. If not, you need to keep retrying (might work better at night) or try a different region.