Is there any way we can retrieve the list of work items(User Stories) in the Azure DevOps that has been carry forwarded to more than sprint.
Thanks,
Suresh
Related
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.
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.
I see that in Azure Devops the billing account is set per organization. So, I can do a cost analysis per organization. Is it possible to do the same thing on a project level with labels and etc? I have checked but I couldn't find any labeling for the projects.
I want to see what is the exact cost of each project based on users, pipelines, parallel jobs costs.
I could not find any billing per project as your question states.
As an alternative or workaround ( I'm not saying this is an ideal solution) you could separate your projects in organizations in order to be able to bill them separately.
Just in case here is the link about billing per organization and here is the link for Billing overview for Azure DevOps in case it may give you some more insights.
Is it possible to do the same thing on a project level with labels and etc?
For this issue , I am afraid this is currently not possible in azure devops . Until now, billing only exists in organization level.
You could add your request for this feature on our UserVoice site , which is our main forum for product suggestions.After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it. Thank you for helping us build a better Azure DevOps.
In addition, for detailed information about billing, you can refer to this document.
I am having trouble creating an Azure Search instance from the preview portal:
Search creation failed in resource group x.
I have tried different combinations of:
resource groups (even created a new one)
regions (East US, West Europe, North Europe)
pricing tiers (both free and standard)
What am I doing wrong?
Just to close on this issue, we have determined that there was an issue with the Azure portal in a recent update that is causing new subscriptions to fail to create new Azure Search services. This would explain why it worked for me but failed for you (as I suspect you have a new subscription).
The Azure portal is working to roll back this change. I am still waiting to get the time but I am hopeful this should happen in the next day or two.
I really apologize for this issue.
Liam
Its advisable to check the limits while planning to create azure search. here are some details:
https://azure.microsoft.com/en-us/documentation/articles/search-limits-quotas-capacity/
Hej!
We have just started using Windows Azure and are now in the phase of designing our infrastructure. A question that I haven't really found a stright answer for is weather there is a limit on how many endpoints I can have per subscriptions. Some research told me 25 and then I found another place saying 150. I haven't found anything on MS offical Azure site or blog.
Does anyone know? and have the limit been confirmed?
Thanks in advance,
Lucas
I think you're confusing subscription with deployment (a subscription is really a billing model for your Azure resources: compute, storage, bandwidth, etc. A deployment will have a collection of VMs (or web/worker roles) living behind a single xxx.cloudapp.net namespace. You'd then configure endpoints at a deployment level. For a Virtual Machine deployment, you'll only worry about external-facing (input) endpoints, since VMs can communicate internally across all ports. For web/worker Cloud Service deployments, you'll also have input endpoints.
Regard the number of endpoints per deployment: This number has grown over the years, and will continue to evolve. I'm not sure of the current limit, but... It's very simple to create an endpoint with PowerShell. With a simple for-loop, you should be able to create endpoints until an error is thrown.