Hello All i have configured a Service Hook for MS Teams in Azure Devops Server which is generating Internal Server Error (500),
I was working to bring Pull request approval, deployment approval to MS team which is documented here https://learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops#approve-deployments-from-your-channel
Response of my service hook
History
Which version of Azure Devops Server do you use? How did you configure the Service Hook for MS Teams? For Azure DevOps Services and Azure DevOps 2020 and later versions, we recommend you use the following suite of apps which offer rich features, to integrate with Microsoft Teams.
Azure Boards app for Teams
Azure Pipelines app for Teams
Azure Repos app for Teams
Related
I cannot find the below configuration in azure devops server (aka TFS)
Please find the below screenshots from azure devops where you can do exactly that
1- Add a public source
2- Add a custom npm registry
3- You can see folio added to upstreams
enter image description here
So why do you think TFS 2019 can't do just that?
It seems to be a new feature, Azure DevOps Service contain the latest feature and we could check the timeline in this site.
And Azure DevOps Server is updated once a period of time. If we check some new feature in the Azure DevOps Service and does not see it in the Azure DevOps, we need to check this Azure DevOps Server 2019 Release Notes and wait for the update.
At the company, we will change the URL for the Azure Devops workspace from https://oldname.visualstudio.com to https://dev.azure.com/newname. We have a lot of connections to Slack in Azure DevOps using two approaches. Older links via service hooks in Azure Devops, new links are via slack applications Azure Repos and Azure Pipelines.
Service hooks in Azure DevOps use Slack's Incoming webhooks, so they will not be affected. However, Microsoft prefers to use its Slack Azure Repos and Azure Pipelines extensions, and the way they work is not clear. E.g. Azure Repos is set up in Slack via /azrepos subscribe [https://oldname.visualstudio.com/projecturl] and this step automatically set the address to azdevchatops.azure.com in Azure Devops Service hooks settings.
So it looks like you need to reconfigure all subscriptions in Azure Repos and Azure Pipelines after changing the Azure DevOps URL. But that is a presumption. It is not mentioned in the documentation and that is why I ask. We have enough connections and that means a lot of manual work to configure everything in Slack via /azrepos subscriptions and /azpipelines subscriptions again.
Does anyone have the experience that when using Azure Repos and Azure Pipelines as Slack Apps, everything has to be reconfigured in Slack as soon as the Azure DevOps workspace address changes?
Notification integration is seamless. Notifications work when you change the name (and URL) of Azure DevOps organisation.
I tested just now and everything is ok.
Note: there are another problem. After Azure Devops organisation URL change you need to reinstall/register build agents again to the new URL. If you use hosted Azure Pipelines in cloud, you need in Project Settings > Agent Pools > Azure Pipelines > Agents disable Hosted Agent and enabled again here. Otherwise, CI / CD pipelines do not work.
I was wondering if it's possible to have TFVS using Azure DevOps Services or TFVS using Azure DevOps Server. Which one is better and how to connect TFVS using Azure DevOps Server. I have experience in connecting it with Azure DevOps Services but I'm wondering the differences with Azure DevOps Server. Thank you
Yes, it's possible; TFVC is exactly the same between the two. You connect to a TFVC repo in Azure DevOps exactly the same way you'd connect to an on-prem instance.
Background info:
Both Jenkins and Azure DevOps are located in Azure. Jenkins is not accessible from internet and is behind organization firewall where as Azure DevOps is not, need an ability to use Jenkins Service hook with mentioned background
Also can below be possible :
possibility to configure Azure DevOps in local Azure VNET
If we can identify or get Azure DevOps host server IP to white-list it for incoming traffic in Jenkins.
The way to link Azure DevOps to your private Azure VNETs, is through Express Route.
Connectivity to Microsoft online services like Azure Storage, Azure SQL, Dynamics 365 and now Azure DevOps is through the Microsoft peering configuration of ExpressRoute circuits.
Route filters are a way to consume a subset of supported services through Microsoft peering. Using route filters, you can enable services you want to consume through your circuit’s Microsoft peering. Azure DevOps is included in the new Azure Global Services route filter with a BGP community value of 12076:5050.
ExpressRoute is available for all Azure DevOps services, including:
Organizations using the new https://dev.azure.com/ URL,
Organizations using the legacy https://{organization}.visualstudio.com/ URL,
Self-hosted Azure Pipelines agents,
Self-hosted Cloud Load Test agents,
Visual Studio Marketplace (https://marketplace.visualstudio.com/),
Visual Studio Subscriber Portal (https://my.visualstudio.com), and
Visual Studio Subscriptions Administration Portal (https://manage.visualstudio.com).
ExpressRoute is not available for Azure DevOps static content that is delivered via Azure Content Delivery Network (CDN), which includes:
Scripts, images, fonts and stylesheets, from the cdn.vsassets.io URL, and
Web extensions from the {publishername}.gallerycdn.vsassets.io URL.
ExpressRoute is available for use with Azure Artifacts. However, you will need to configure route filters for the Microsoft Azure region that your organization is located in.
See also:
https://devblogs.microsoft.com/devops/expressroute-for-azure-devops/https://devblogs.microsoft.com/devops/expressroute-for-azure-devops/
https://learn.microsoft.com/azure/expressroute/how-to-routefilter-portal
I have been struggling to find a guidance or best practice documentation for new Azure Tenant who want to start the Azure DevOps Service journey.
The Azure DevOps documentation is created in a piece meal approach and there is no proper documentation about such guidance and it is maddening to scan through several Azure DevOps product/feature to figure out the content I wanted.
From the documentation, I understand that one needs to create Azure Organization and project structure etc. and then users within the AAD (Company's MAC tenant) can be added to Organization or at project level to collaborate.
But if I am a new Organization or Entity that has just acquired a Azure Commercial Cloud subscription then what are the guidelines to setup my Azure DevOps organization?
E.g. Do I have to be a Global Admin of my Azure Commercial
Subscription to first start the Azure DevOps Organization? Or can I be
a Admin for Dev/Test Subscription and then start the Azure DevOps
Organization? Can I use my Dev/test subscription to create Azure
DevOps organization? What are some limitation or restruction with regard to my Azure Subscription in terms of ability to create Azure DevOps organization? What roles are advised to initiate the Organization creation process?
Where is the guidance documentation or best practice documentation around it so we can put a proper governance structure on Azure DevOps - organization/project and users etc.
Here are some high level prerequisite for setting up Azure DevOps Service:
You must have a tenant in Azure Commercial or Public Cloud. You can still deploy and build on other cloud or on-premise. You need public cloud to host your DevOps Org and project configuration and optionally to host the git based code repo.
You need a Subscription in Azure Public cloud tenant
You will need a user with Account Admin, Service Admin or Subscription Admin level privileges to create first DevOPs Organization
After creating the DevOps Organization, Users (scrum master, Managers, developers and testers ) can be invited to these organization from DevOps Organization settings
Users who have Visual Studio (VS) Enterprise licenses will see most of the features in the Azure DevOps Service Organization. So having a Visual Studio Enterprise or professional license subscription is useful and these users are counted as free for Azure DevOps service user pool. These VS license already come with benefit attached and part of those benefit is the access to Azure DevOps service.
It will be greatly beneficial for Admin team (devOps Org management team) to try to understand how Azure DevOps Service Access levels and permission works and how they are mapped to different Visual Studio licenses and how to configure these access for different role of users. You can find useful information in this regard on AzureDocs.
You do not need to have Visual Studio license (it is optional) to use Azure DevOps Service. By default Azure DevOps service is free for small team of 5 developers with limited access to features. So small organization can immediately start using it within their Enterprise Account or Pay-as-you-go subscription. You can add users to your Azure DevOps Service organization irrespective of if they have VS licenses and you can pay for their subscription on a monthly basis.
Also, I will highly recommend training course from Microsoft Learn website on Azure DevOps Service to get excellent understanding of prerequisite and features of Azure DevOps Service. Just search for DevOps keyword and you will find number of courses with different modules that will provide step by step instructions on setting up your first Azure DevOps Service Organization to integrating with GitHub and building pipeline, static code analysis etc.