I am trying to find a way to migrate all projects (+600) from our Gitlab server to our DevOps platform. Are you aware of any scripts/automation?
Thank you!
I tried different tutorials from Microsoft. They are however designed for single project migration (usually GUI). Yet, in this case, we have multiple users and multiple projects.
Related
The goal I'm trying to accomplish is migrating out of CVS to using Azure Repos. Currently BAR deployments are sent through CVS repos and then deployed to IBM Integration Bus. I would like to accomplish this same process through Azure DevOps.
I know this extension exists:
https://marketplace.visualstudio.com/items?itemName=ms-vsts.ibm-integration-bus&ssr=false#overview
However there is limited documentation available. I'm curious to know if anyone has had success using the above extension?
If not through the extension is there another solution available?
I have never used that extension myself.
The tasks involved in setting up a build and deploy pipeline are not difficult, so you should be able to roll your own.
See mqsicreatebar and mqsipackagebar for how to build the BAR files.
See mqsideploy for details of how to deploy the BAR files.
The rest will depend very much on your chosen source code control system and build orchestration technology.
A few years ago, our team made the full transition to Azure DevOps. Before that, we had a mixture of on-prem TFS and Subversion but went to the Azure DevOps as it was easier to maintain project status between our developer and BA teams. At that time, for each project the team was working on, we just created a new "project" in Azure DevOps, but over the course of the past few years, we have found that using that method doesn't lend itself to helping us track metrics across all of those projects. We also see that maintaining multiple, separate backlogs is not ideal as we have developers spread across multiple sprints at the same time in different projects without a single place for the team leads or scrum master to fully know what their team members are working on in a single day.
Now, we've made use of queries, but those only go so far, so we've made the decision to merge our projects into a single "project". My scrum master and I have been looking at Naked Agility's merge tool, as outlined in this link: https://blog.devopsabcs.com/index.php/2019/06/12/one-project-to-rule-them-all/.
Has anyone used this tool and how well did it work for you? Also, are there any other options for merging projects together as this tool seems really complex (which the developer states is the case).
Azure DevOps: Merging two projects together
Sorry for any inconvenience.
I am afraid merging projects into a project is currently not supported in azure devops.
There is a Under Review user voice about make it possible to move a Team Project between Team Project Collections.
Merging two projects is not a simple task, it contains not only source code, build/release history, workitems and other watch outs were mainly around access and security:
External API integrations such as Web Apps, Function Apps, JIRA, Service Now
External inbound app authorisations
External outbound app authorisations such as Azure Service Principals
Variable Group authorisations to YAML Build Pipelines
Library reference updates including KeyVault
etc
This refactoring ended up being much more work than the code merge itself.
Besides, there is a Azure devops extension Migration Tools for Azure DevOps, which allow you to migrate Teams, Work Items, and Plans & Suits from one Project to another in Azure DevOps/TFS both within the same Organisation, and between Organisations. Watch the Video Overview to get you started in 30 minutes. This tool is complicated and its not always easy to discover what you need to do.
Hope this helps.
we are trying to migrate from TFS to Azure Devops and as part of the migration want to migrate work items. I had tried using VSTS-work-item-migrator and vsts-sync-migration tool for migration but couldn't be succesfull in doing that as there are some customized WIT's in current TFS.
Can anyone suggest what would be best approach to do migrate without any data loss.
Note: We don't want to use import database approach.
For your demand,I am afraid there is no such tool available at present.These migration tools should not recognize your custom process.So it is not feasible to migrate custom work items to azure devops via tools.
To migrate complete data from TFs to azure devops, it is recommended to use the method of importing the database.
This is guided in other case and docs. For details,you can refer to these.
TFS to VSTS migration - The official import option which will import 1 project collection into 1 VSTS account. It automatically imports everything stored in the backup. At the point of writing this, the TFS must be upgraded to TFS 2018 and some work item template customizations must be removed (there are a few well documented features unavailable on VSTS).
There is tool call nkd-agilty migration tool which is used from all kinds of migration from tfs/AzureDevOps to another
https://nkdagility.github.io/azure-devops-migration-tools/
The tool we are trying to integrate with vsts(Azure DevOps) is Cognos Framework Manager. Is Cognos Framework Manager anyway compatible to integrate with vsts. In what way will i be able to acheive this. I was just trying to get ideas from PowerBI to understand workflow of BI projects. But its quite different from Cognos Framework Manager. This is in regards to testing the workflow of Cognos projects & their CI/CD pipeline.
One of FM's selling points used to be it's native integration with source control but that feature was taken out when it was no longer in a competitors feature list.
Having said that, Framework manager is just a bunch of files. Just commit those files to a DevOps github repository using for example git command line.
With regards to automatic deployment from DevOps to your environment, you'd need to work out how to use the FM API. Some info here but I'm not going to take the time to decipher it
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.dg_fm_sdk.10.2.2.doc/c_sdk_overview.html
In the very least you'd need to install FM in your DevOps deployment agent
I am in a microservices project where we are creating around 120 microservices. How do I configure azure devops for this project? Do I have to create a new project for each microservice? I would like to keep the dash for project monitoring
I would recommend that you create an organization and a project.
Then you can use create a git repository for each microservice, 120 microservices in 120 repos.
You can read about how Microsoft uses git here.
TL;DR version quoted below.
Mono Repo or Multi-Repo with Git
It's worth pausing to reflect that this isn't the only way. While
we've elected to have a single monolithic repository (the
"mono-repo"), other products at Microsoft use a multi-repo approach.
Skype, for instance, has hundreds of small repositories that get
stitched together in various combinations to create their many
different clients, services, and tools. Especially for teams embracing
microservices, multi-repo can be the right approach. TFS/Azure DevOps,
like many products at Microsoft, began as a monolith, and its code
organization reflects that