we upgraded a TFS2017 to Azure Devops Server 2019.
We had a custom XML process template on TFS2017 that we want to migrate to inherited processes. But we cannot see this process template in the process page. We only see the inherited processes (Agile, CMMI, ...) and the basic XML templates which where migrated ("Microsoft Visual Studio Scrum 2013.3", "MSF for Agile Software Development 2013.2", ...)
There is a project with this custom template and we can update the process with WIT commands.
Does anyone know how to make this custom process visible in the process page? then we will be able to migrate it.
Related
We are currently using Team Foundation Server 2017 and want to migrate to DevOps Server 2020,
We created new DevOps Server 2020 and created new process template, we modified the built-in Agile process template by adding a new workflow and new columns to some work items.
I need to know how to migrate the old projects on TFS 2017 to DevOps 2020 and change the process templates to the new the process template we created.
Thanks
how to migrate the old projects on TFS 2017 to DevOps 2020
For this requirement, we cannot migrate only the project to another new Azure DevOps server.
This feature is not supported.
Currently we can migrate the project collection to the new server.
For more detailed steps, you can refer to this doc: Move a project collection
Change the process templates to the new the process template we created.
According to this requirement, you need to determine whether the process on your Azure DevOps Server 2020 is inherited or XML.
As far as I know , TFS 2017 only supports XML process.
If you are using XML process collection in the Azure DevOps Server 2020, you can export the XML process and import the process to the migrated Collection.
If you are using inherited process collection in the Azure DevOps Server 2020, I am afraid that you can't change the old XML process to the new inherited process.
For more detailed info, you can refer to my another ticket: How to upgrade a Team project to use the Inheritance model
I am moving from TFS 2015 to Azure DevOps in the cloud.
Following the migration guide I have done the following:
TFS 2015 -> TFS 2018 -> DevOps 2020.
When running the Migrator tool I am getting an error. The OTB process has errors in them.
If I don't care about the changes made in my process is there a simple way to get to the OTB process?
The Process validation error in TryMatchOobProcesses.log file would block your projects
from landing in the inherited process model(OTB process). But You don't have to fix these errors. They will not prevent you from doing an import. And all your customizations will be imported to Hosted XML process model.
See below extracts from the Process template validation.
If the project was created with the Agile, Scrum, or CMMI process template, and was never customized, the project will use the Inheritance process model. In all other cases, the data migration tool considers the project as customized, and the project will use the Hosted XML process model.
TryMatchOobProcesses.log - Lists for each project the target process model - Inheritance or Hosted XML. For projects that are set to target the Hosted XML process model, it explains why they are considered to be customized. You don't have to fix these errors, but they give you guidance what to do in case you want to migrate into the Inheritance process model
And now DevOps 2020 services supports Moving from Hosted XML Process to Inherited Process. See the below official documents for more information about what you need to pay attention to when moving to Inherited Process.
Clone a Hosted XML process to an Inheritance process
Change a project from Hosted XML to an inherited process
So according to Document and the Migration Guide(Page-33), you can just import the process without fixing the Process validation error in TryMatchOobProcesses.log. After the process is imported to Hosted XML process. Then you can change it to the Inheritance process.
I have a requirement to change the layout of the Task in Azure DevOps Server 2019. I want to relocate the "Details" section under the "Staus" section. I tried using the Process editor via VS 2019. But doesn't work published WIT show no modifications. Can anyone guide me through this?
Layout change I did:
Additional Note:
I tried following the inherited process model but got stuck. According to this article some links are missing on our DevOps Server 2019. I logged in as the administrator of the DevOps server. Please refer to the screenshot attached.
In Azure DevOps, we do have two process models,On-premises XML process model and Inheritance process model.
For Azure DevOps Server 2019, you have a choice of process models. When you create a project collection, you'll need to choose between On-premises XML process model and Inheritance process model.
Using the Process editor via VS 2019 only apply to On-premises XML process model.
If you are using inherited process, you need to do the customization in web portal directly-- Customize the web layout for a work item type (Inheritance process)
More details about the customization of these two models:
About process customization and inherited processes
On-premises XML process customization
We migrated a project from TFS 2015 to VSTS recently as a Scrum project as it was in TFS. But we want the project to be using the CMMI process template.
Now, how can we migrate the existing project from Scrum to CMMI process template?
According to MS documentation (here) ...
You can change the process a team project uses from a system process
or inherited process to an inherited process. You can only change team
projects to use another process that inherits from the same system
process. That is, you can change an Agile-based team project to any
process you created from the Agile system process as well as to the
Agile process. Whereas, you can't change a Scrum-based team project to
an Agile-derived inherited process.
But you could still create a new team project based on CMMI and then move your source code and workitems to that new team project. To move workitems you can export them to Excel, create a new Excel connection to VSTS, that is connected to the new team project, and then copy the workitems and pushing them from the new Excel file into the new project.
You can custom a process when using Hosted XML, the changes made to the process template are then applied to all team projects using that process.
More information: Customize a process when using Hosted XML
We have Continuous Integration setup through TFS 2012.
Requirement:
Wanted the release build to be deployed on mulitple servers as a part of the CI. We need to do a xCopy of the files onto the server folders.
On TFS with Azure there seems to be a facility to publish it directly onto the server (http://www.windowsazure.com/en-us/develop/net/common-tasks/publishing-with-tfs/)
There-in it uses 'AzureContinuousDeployment.11.xaml' as the Build Process Template.
Wanted to check if anybody has tried similar publishing for custom/local servers, maybe using Custom deployment template, etc.
You likely want to create Standard Environments for Automated Deployment and Testing which you can do out of the box with TFS 2010. TFS 2012 and TFS 2013.
You use the "Lab Centre" which is part of the Microsoft Test Manager product to configure Environments that consist of one or more target machines.
You then use the Lab Default Template to push a build output to the target servers and execute a script to complete the install. You can even have your Integration and UI tests executed as part of the same actions.
If you are looking for more integrated Release Management with Team Foundation Server then you should look to Octopus Deploy as a good way to go all the way to production.
We use it with many of our customers and it works a treat...
From my understanding TFS 2012 ships with a Lab Deployment template. You configure the lab definitions of which servers are involved and then configure the deployments to those servers. Also used for hooking Test Manager in to run unit tests in the lab.