I want to setup Azure DevOps organization wide. For that, we have decided that we will set up a single Azure DevOps organization and every team will work underneath this organization as separate project. The only challenge which I am getting is to determine the cost incurred by each project. Azure DevOps generates bill at organization level however we want to know how much a specific project incurred cost so that we can charge that team accordingly. I am not so much aware about azure devops billing prospects. Any insight would be very useful to me.
Currently there is no way to determine the cost incurred by each project, As you know the paid services(eg, paid basic access for users, paid ci/cd, paid test plan, etc) in azure devops are billed at organization level.
You can submit a suggest for such feature to be developed. Hopefully the development team will consider it and develop this feature.
You may have to manually calculate the paid resources(paid users, ci/cd(I found the build usage extension can be used to analyze ci/cd cost), paid test plans) that used by each project, and calculate a rough cost until the cost view for each project is developed.
You should be able to set unique custom tags, using the same per each specific project. Then from there you should be able to have cost propects based on tags specified by grouping on tags [1].
[1] https://learn.microsoft.com/en-us/azure/cost-management/quick-acm-cost-analysis
Related
We have a scenario where we need to migrate more than a 100 projects that are in one ADO organization to another ADO organization.
Is there way how to do perform this migration org to org?
We have tried using the Azure migration devops tool by installing it in DEV test lab in A tenant and installed the tool.
Started with workitem migration but couldn't due to the errors.
So is there a way out to directly migrate org to org in two different ADO's?
There is no built-in way to migrate projects from one Azure DevOps organization to another. However, there are a few ways to accomplish this:
Use the Azure DevOps Migration Tools.
Use a third-party tool, such as OpsHub Integration Manager.
Manually export and import the data using the Azure DevOps REST API.
Currently, there is no supported method to move an organization directly to another inside azure devops, and you could follow this user voice ticket for the upcoming feature. make it possible to move a Team Project between Team Project Collections
As already shared in previous answers, there is no direct way supported by Azure currently, to migrate an org from one ADO to another ADO. There are a few third-party migrations tools that support this use case. When selecting migration approach, here are a few factors that should be considered, as these are often over-looked and cause trouble during the migration process:
What data can the migration solution migrate?
As there is no direct (Lift and shift) way supported by Azure to migrate, all third-party tools use ADO APIs to move data. As a result, there will never be zero data loss, e.g., no tool will be able to retain work item ID across ADO orgs. You need to list your must–have requirements (e.g., history, mentions, inline images, source code, work items, test management etc.) and then choose a tool that can meet most of them.
Can users continue to use source ADO, while the migration is going
on?
Downtime adds operational costs and impacts development operations as teams cannot use ADO during ongoing migration. Anticipate downtime required for scenarios which may cause further business disruption.
Time and monitoring required to migrate data?
If the migration tool is migrating projects one by one, it can take a lot of effort and time to migrate the data spread across 100+ projects. Understand how many projects can be migrated in parallel to have a speedy migration and minimize disruption.
What level of skills will be required to use migration tool?
Some tools are a collection of unsupported beta versions of scripts, requiring a very high degree of sophistication. These can be again highly time-consuming, error-prone, and can hinder operations. Analyze what part of migration may require script and involvement from your side.
As captured in the previous answer, OpsHub provides a Migration tool, OpsHub Azure DevOps Migrator (OADOM), which helps you migrate projects from one organization to another ADO organization. It provides rich data migration, including history, attachments, inline images, user mentions, etc., for a wide variety of data sets, including source code, test assets, work items, Area, Iteration, etc.
Please reach out to OpsHub’s Migration Experts to discuss how to migrate the projects from one ADO organization to another.
There is a roadmap feature in JIRA, through which we can create Epics, user stories and assign start and end date to them itself by simply dragging the horizontal bar in table.
With help of this feature we can perform month-wise/day-wise or quarter-wise planning for any project. Additionally, we can export and share with client too. I require this kind of user friendly feature in Azure DevOps too. I tried integrating a Epics and Features Roadmap Plugin, but its not giving precise results as JIRA Roadmap is giving. Its user interface is very confusing, giving some occasional error message. Plus, it configuration is also very tedious and time-consuming. Can I get better user friendly GUI in Azure DevOps for Roadmap creation?
Please Help. Attached screenshots for reference of both platforms feature. Thanks in advance.
DevOps provides Delivery Plans to review the schedule of stories or features your teams plan to deliver. Delivery Plans show the scheduled work items by sprint (iteration path) of selected teams against a calendar view.
If it doesn't meet your requirement, you could check the existing extensions to see whether there are extensions useful:
https://marketplace.visualstudio.com/search?term=roadmap&target=AzureDevOps&category=All%20categories&sortBy=Relevance
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/
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
Microsoft Planner or Azure DevOps
We need to keep a track of tasks assigned to DevOps teammates.
I checked Azure Devops.
Azure DevOps gives you tasks and issue so that you can assign it to the members.
Not sure what MS Planner offers and should we chose that over Azure DevOps
Microsoft Planner is a task planning tool integrated in Office 365.
The level of capability from low to higher is corresponding task management to project portfolio management.
For a detail tutorial you could take a look at this link: Microsoft Planner - Step-by-step guide for users
Azure DevOps is a cloud-side source code management system also offering project management features as part of Microsoft's application life cycle management solutions. More project management features are accessible.
In Azure DevOps, you could also track work with Kanban boards, backlogs, team dashboards, and custom reporting.
Combine drag-and-drop sprint planning and flexible work item tracking with comprehensive traceability to have the perfect home for all your ideas–big and small.
You could also use the visualization options provided by Delivery Plans to review the schedule of stories or features your teams plan to deliver. Delivery Plans show the scheduled work items by sprint (iteration path) of selected teams against a calendar view.
Delivery plans is also interactive. You can change the assigned sprint of a work item by dragging it to a new sprint as shown in the above image.
I couldn't directly give you an accurate answer which one is better, it's all based on you and your team's requirement. They are totally two different products. Please kindly select the one suitable for your sides.
We have several closely related DevOps projects each with their own jazz git repositories in our Bluemix DevOps account. Each project has its own stories/tasks/defects etc.
What is the current best method to gain a single view of the cumulative backlogs of all projects so we can have one place to prioritize items and plan sprints across all projects. If DevOps Track and Plan can not do this. Is there a 3rd party tool that can integrate with DevOps/Bluemix that will do this for us?
Not a perfect solution, but I asked a very similar question and have had success using the approach described for several projects:
How to manage multiple components with IBM Bluemix Track & Plan
This isn't a supported capability at the moment.
I've passed your question on to DevOps Services' developers. We're adding features to Bluemix and Bluemix DevOps Services all the time.