TFS 2015 XAML Builds migration to Azure DevOps - tfs

We migrated from TFS 2015 to Azure DevOps. The XAML builds also ported over to Azure. But we need to migrate them to Azure build pipelines as the XAML builds are still running on On premises TFS Server. We have hundreds of builds and cant manually create new pipeline for each build one at a time. Can some one help please?

XAML builds are still supported with Azure DevOps Service (with some limitations), see official response from Microsoft, in my answer here.
We're currently in the process of migrating from TFS to Azure DevOps and we're not planning on upgrading any of our legacy XAML builds (we're creating vNext builds going forward), as they were successfully migrated into Azure.

I figured out a way ( I am not done yet)..
we can call the api and export the build defs into json files
Use the Json files to port them over to the new Build defs. (Porting involves creating new builds programatically and using Azure Api .. + the data from Json files we just exported).

Related

How to migrate a TFVC project from TFS to AZDO?

How to migrate a TFVC project from TFS to AZDO ?
Goal:
Is to migrate host projects on (TFS 2017) using TFVC, to switch them to Azure DevOps Service (AZDO) using TFVC there too.
My context:
TFS 2017 server version 2 hosting current source projects.
AZDO 2019 service wanting to host projects targeted on TFS.
Context wish:
Keep the history of source projects (TFS) on AZDO services.
I Just want to migrated the projects (TFS) in TFVC to (AZDO) in TFVC, without doing any TFVC -> GIT conversion.
I would like to avoid updating the TFS 2017 server for 2018 then to
the AZDO server to switch to AZDO services afterwards.
You understand
that is a lot of step to just want to switch a project in TFVC on
TFS2017 to a TFVC on AZDO
The easiest way to migrate is to upgrade your TFS2017 server to Azure Devops Server 2019 and then using the full fidelity import feature to upload your whole database backup to Azure Devops Service.
At the moment migration tools support TFS2018u3 as well as Azure Devops Server 2019 and 2019u1 as well as 2020 can be imported into the service. We do these kinds of imports regularly and it's a very straightforward process to restore your TFS server backup to a temporary SQL server, install the correct version of TFS/Ads and have it perform the upgrade in-place during the installation. Then use the migration tools to import the collection into Azure Devops Server. Depending on the size of your collection this may take between a couple of minutes to a couple of hours. I've done the upgrade on my laptop on certain occasions as well, installing Azure Devops Server and SQL Server Developer edition directly on Windows 10. Even a trial versions will do.
For all the details on the. Import process, see:
https://learn.microsoft.com/en-us/azure/devops/migrate/migration-import
If you want to import your tfvc project from one TFS servers to another TFS server/Azure Devops Server, you can detach the project collection on you current TFS server and bacmup/restore the database on another server. It will automatically be upgraded
If your project collection has multiple projects, you can delete the projects you don't need after attaching and upgrading your collection.
There are a few tools to perform a history replay from one server to another, those tools can't import everything, your changes id's will change and you'll lose the exact date a commit was made (and possibly the user who made the commit if that account no longer exists). Tools like:
https://www.opshub.com/products/opshub-visual-studio-migration-utility/
Depending on how old and how big your collection is, it may take many hours to migrate the data. If data has previously been deleted/destroyed or branched across projects or edited during branch operations, then the replay may fail or may be forced to perform alternative actions, some of these operations are no longer supported. I've used opshub on a couple of projects and some it completely failed to migrate, others migrated with incomplete or incorrect data. This was 4 years ago, maybe these were bugs and they were fixed, but since the import tools have been released we've used those almost exclusively.
PS: using tfs-git to convert (part of) your TFVC repo to git would be an alternative which I'd recommend you look into further. TFVC has been declared feature complete and has received very little love in the past few years. It's not supported by the new Multi-stage YAML pipelines, the integration for VS Code has been deprecated, the cross platform commandline tool for tfvc has been deprecated and therefore support for eclipse and rider and intellij as well. Team Explorer in VS 2019 is now pushed to the background with the release of the new git features which have escaped the Team Explorer window. It's clear that TFVC is fighting for a lost cause and that Git is winning, you'll need to switch over at some point.

Migrate from TFS 2010 to Azure DevOps online

I want to migrate form TFS 2010 to Azure DevOps online and was following Azure DevOps Migration Guide.pdf and running into issues when trying to validate my project collection.
On the other hand I had to see other MSFT documentation and it tells a different path:
Where as Azure DevOps Migration Guide says:
What is the best way to migrate from TFS 2010 to Azure DevOps online ?
Look closely. One document is more recent than the other. The first screenshot shows Azure DevOps Server 2020 as the end point. The other shows TFS 2018.
You need to upgrade to the most recent version of Azure DevOps Server in order to migrate to Azure DevOps cloud. The "best way" is always to follow the most recent official documentation.
If you're looking for help with performing the migration, you need to ask a new question that asks a specific question about the issue you're encountering.
We recommend that you use data migration tool to migrate data from Azure DevOps Server to Azure DevOps Services.
The data migration tool for Azure DevOps supports the two latest releases of Azure DevOps Server at a given time. Releases include updates and major releases. Currently the following versions of Azure DevOps Server are supported for import:
Azure DevOps Server 2019.1.1
Azure DevOps Server 2019 Update 1
Please update your TFS version and then Migrate your server to Azure DevOps

Implementing Azure DevOps Services with On-premise TFS Release Manager

We have Release Management for VS 2013 running for all our builds and releases on-premise. We are not ready to publish our systems to Azure Cloud yet, but would like to migrate our source-code to Azure DevOps Services in the mean time. We are also not ready to publish via Azure DevOps Pipelines to agents installed on our servers. Is it possible to have your source-code in Azure DevOps Repos, build the source using either Microsoft-hosted or self-hosted agents and then have Release Management for VS2013 release them to our environments?
I am able to do normal published via Azure DevOps Services totally to Azure Cloud, and even to on-premises with distributed agents running on servers, with test applications, but this would mean I have to recreate every build definitions, we have created, again in Azure DevOps, and also that we would bypass our Release Management server.
We would like to stick with Release Manager for now for releases, but want to migrate our source-code and work-items into Azure DevOps and build source in Azure DevOps Pipelines.
It's unlikely to work. Release Management Server 2013 only supported XAML builds. 2015 had support for JSON/visual designer builds, but the support wasn't particularly robust. I'm not even 100% sure that RM Server can communicate with a modern Azure DevOps instance. You're using a 6 year old tool that's been deprecated and unsupported for several years; you're not going to find a lot of options to keep it working properly with modern, supported tools.
There is a tool that can extract PowerShell deployment scripts from RM Server that can be used (with some degree of rework) in an Azure DevOps pipeline, but it's not a perfect solution. And I say that as the primary developer of that tool.

Jenkins plugin "Visual Studio Team Services Continuous Deployment" throws NullPointerException

My system is an on-premises setup for TFS 2015 and I am trying to get Release Management working with my Jenkins continuous integration system. I have recently added the ""Visual Studio Team Services Continuous Deployment" plugin to Jenkins. After finding out that I need to have Basic Authentication enabled on my TFS server to avoid a 401 - Unauthorized: Access is denied due to invalid credentials. error I am getting to the next error: NullPointerException.
I have looked through the code for the vsts-cd-plugin to see that there is an explicit reference to this API call that I don't believe is in TFS 2015 Update 3...
"/_apis/release/releases?api-version=3.0-preview.2"
Has anyone been successful in using the vsts-cd-plugin with Jenkins and an on-premises TFS 2015 setup? Does anyone have a suggestion on how I can fix this problem to create a TFS Release from Jenkins?
The API version 3.0-preview.2 is for Visual Studio Team Services, it is not included in On-premise TFS. In On-premise TFS, you need to use 2.2-preview.1.
api-version = 3.0-preview.1
Using on-premises: An earlier, and slightly different, version of this
Release Management API is available in Team Foundation Server 2015
Update 2. To use, you must specify an API version of 2.2-preview.1.
New release references a release definition to deploy an application
comprising of one/
You can try to download the source code of the plugin and update the API version and then build it on your local machine and install it in Jenkins.

Depoy SSAS Project from VSTS to local development server using DevOps method

We are using TFS agile process in our MSBI project. I am new to VSTS. We created new team project into VSTS and we checked in our SSAS project into VSTS. Now we have to deploy SSAS project from VSTS to local development server. First I tried to build the project from VSTS. It's not worked. I googled but I couldn't find any solution.
Can anyone please tell me how to build and deploy SSAS project from VSTS to local development server step by step?
The SSAS projects can be build with the Visual Studio Build step.
The deployment of .asdatabase files (which are the output of the build) can be done with Microsoft.AnalysisServices.Deployment.exe

Resources