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.
Related
How do I automatically renew PAT for Azure DevOps on-prem installation?
I see a similar post but there was no solution.
Generate a PAT for an on-prem DevOps installation using API.
All the articles and examples I'm seeing are related to Azure DevOps Services(cloud offering)
My VMs all have Azure DevOps agents installed on them to automate deployments. We have a need to automate runbook tasks on these agents as well, and are investigating Azure Automation as a solution.
However, I would prefer not to have to install two agents on every VM. Is there a way to have Azure Devops and Azure Automate share an agent on a single VM?
I suppose that you could test to create a combination with Azure DevOps and Azure Automation.
And the key to for the integration is creating a service connection from Azure DevOps to Azure Resource Manager.
And you could try to finish your Azure Automation Deployment with Azure Powershell task in a release pipeline.
And you could refer to this blog for more detailed instructions. USING AZURE DEVOPS PIPELINES WITH AZURE AUTOMATION
I need to export variable groups from one azure devops to another azure devops project. How can I do this?
The UI of Azure DevOps doesn't provide such a functionality. This blog explains how to do it using Azure CLI and the Azure DevOps extension for Azure CLI. If you're new to the (Azure DevOps extension for) Azure CLI, then please read my blog to learn how set it up.
Can I use this tool for migrating workitems from OnPrem to Cloud version of Azure DevOps?
We can use the data migration tool for Azure DevOps. This tool provide the high fidelity way to migrate collection databases from Azure DevOps Server to Azure DevOps Services.
This means you can also use this tool to migrate your workItem from Server to Cloud.
You can refer the guidance doc: Migrate data from Azure DevOps Server to Azure DevOps Services
And here you can download the tool:https://www.microsoft.com/en-us/download/details.aspx?id=54274
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.