I'm trying to setup TFS publishing from within the Azure Management Portal.
After authorization, one is suppose to select a project. But all I get is:
Your TFS account has no projects
But my TFS account certainly has many projects, I can see them when logging in there.
What have I missed?
Oh, just found this.
Nothing you did wrong. Deploying from TFS's git repository to Windows
Azure is not yet supported. It is on our radar tentatively mid of
this year.
The reason seems to be that my project(s) are Git repositories. (Not TFS repositories)
(turning a comment into an answer)
Until Azure supports web site deployments directly from TFService hosted Git repositories you can use an automated build to do the deployment.
Details on how are at http://www.richard-banks.org/2013/08/how-to-deploy-azure-website-from-git_21.html
Related
I am trying to determine how to backup the online ADO account that I created on Microsoft's servers so that I can restore it on my own physical server. I have a few projects already started along with work items, repositories, pipeline jobs and NuGet artifacts already in place. It would take quite a while to rebuild the projects manually, not impossible, just not desirable.
I have looked and have not found any resource as to how to perform this or if it is even possible. Any help from someone who knows would be greatly appreciated!
Currently there is available extension: Azure DevOps Migration Tools, which allow you to migrate Teams, Work Items, Plans & Suits, and Shared Queries, & Pipelines from one Project to another in Azure DevOps/TFS both within the same Organization, and between Organizations. See: https://nkdagility.github.io/azure-devops-migration-tools/ for latest guidance.
In addition, for repositories, there is no such extensions, you could try to clone an existing Git repo and then push it to a new remote repo server.
BTW, you could use Rest APIs: Artifact Details to get artifacts and then publish them to new feed on Azure DevOps Server.
Is there any way to migrate a single team project from TFS 2012 Update3 /15 to Existing Azure DevOps Services with the change set history and work items?
Please let me know if there is a process to get it done.
Thanks in advance :)
There is no out-of-box feature to migrate team projects between TFS to DevOps, you may try #Shamrai's suggestion, or check some third party tools, like OpsHub: https://marketplace.visualstudio.com/items?itemName=vs-publisher-1455028.OpsHubVisualStudioOnlineMigrationUtility
There is no method to migrate one single team project. However, you can try to:
Upgrade your current TFS to Azure DevOps Server (Upgrade your deployment to the latest version of Azure DevOps Server).
Use Migration Tools for Azure DevOps to migrate work items. (TFS 2017 Migration To VSTS with VSTS Sync Migrator)
Import your TFVC repository into GIT (Import repositories from TFVC to Git) and move it into Azure Devops project (Import a Git repo).
Is it possible to connect on-premises TFS source control to Azure Visual Studio source code repository? If so, could you please write down the steps involved?
So far I haven't found anything by googlying for the question. The only way I can think of is to write a job in the Windows task scheduler that will pick up files from on-premises source control and send them to the Azure TFS. I havent done that get but with some effort it can be done.
Is there any other straight forward way of achieving the results?
If you mean to connect TFS to VSO you can do this with the TFS Integration Tools with a two way sync. Be warned that this is a really silly thing to do and I would not recommend it.
A better solution would be to simply move to VSO. You can use a one way sync with the TFS Integration Tools or OpsHub. Once there you use VSO as the primary.
You can still install and use a local TF Build server or a local Release Management server so that you can build and deploy locally.
You can even configure AAD integration to create single sign on from your local domain.
http://nakedalm.com/use-corporate-identities-existing-vso-accounts/
http://visualstudiogallery.msdn.microsoft.com/eb77e739-c98c-4e36-9ead-fa115b27fefe
We have a VSO repository with multiple sites in the same solution. We want to be able to deploy our sites independently of each other to Azure with continuous delivery. Right now the first site alphabetically is deployed to all our sites which of course is not desirable.
Is this possible to achieve?
I have tried to set the Project key to the correct csproj in App Settings like suggested here: https://github.com/projectkudu/kudu/wiki/Customizing-deployments without any success. Maybe Kudu is not used for VSO?
Any help would be greatly appreciated!
You should move away from trying to do this in a build, especially if you want that level of control.
You have Release Management Online provided with your VSO account and can use the Release Management client to configure your releases.
I believe that you can right-click on your Build and have an appropriate starter release template created when configured.
http://nakedalm.com/create-release-management-pipeline-professional-developers/
Here is an example of and end to end deployment with a web app. Deploying to Azure with RM is Childs play...
I'm currently working with Team Foundation Service in combination with Windows Azure. I've created a Website in Azure and setup TFS publishing.
Everything is working perfectly except I was wondering how to configure different branches.
This article explains how you can use Git to configure different websites to point to different branches. It says:
In this example, I’ll be using GitHub.com to manage my source code.
You don’t have to use GitHub.com for this, so if you’re new to Git
don’t freak out, you have other options like CodePlex, BitBucket, or
TFS. Heck, you could even automate an FTP deployment if you want to.
However, I can't find the branching option for my TFS publishing configuration. Am I missing something? Is this a Git only feature?
After searching the web and having some contact with Microsoft I found the necessary configuration steps.
These are the things you have to do:
Link the two websites to your team project
Branch your code
Adjust the workspace mappings on the build definition to the staging site to map the branch
Change the solution to build property on the build definition for your staging site to point to the solution in your branch
I wrote a blog post about it that explains it in more detail: Branches, Team Foundation Service and Azure Websites