I have TFS repository for my Java maven project. I want to access that project in Azure DevOps by creating new pipeline.
In Azure DevOps we have 5 options, one of them says to Create new Pipeline via TFVC where it asks for Repository URL (Connection URL).I mentioned Connection URL but still project structure is not displayed in Azure DevOps.
I also tried adding a new service connection(Add azure repos/Team Foundation Service connection), but it is not verifying connection.
I gave Connection Name,Connection URL Username and Password.
Error which I receive is - Failed to query service connection API.
In short ,my TFS project is not importing in Azure DevOps. Please suggest what am I doing wrong.
Guess you were talking about Azure DevOps Service. Since Azure DevOps also have a server call Azure DevOps 2019 which actually is the latest version of TFS at present.
There maybe some misunderstanding. It's not able to directly access any TFS on-premise repository from Azure DevOps Service.
You need to migrate data from TFS to Azure DevOps Services by using the data migration tool.
The data migration tool helps you bring your data from Azure DevOps
Server to Azure DevOps in the cloud. Keep the same work item numbers,
Team Foundation Version Control check-in numbers, Git commit IDs, and
much more after you land in Azure DevOps.
But it do have some limitations of this tool. For example it only supports the two latest releases of Azure DevOps Server at a given time. Currently the following versions of Azure DevOps Server are supported for import:
Azure DevOps Server 2019.0.1
Azure DevOps Server 2019 Update 1
If you just need the source code in TFS repository without keeping any history, work items. The simplest solution is creating a new repository in Azure DevOps and download your code to your local repo from TFS. Finally commit/check in your local repo to your Azure DevOps Service.
If you are using TFVC in your TFS server and want to use Git in Azure DevOps Service. Then use git-tfs as a two-way bridge.
Related
I was going through doc "" https://learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops"" which says integration of Azure Pipelines with Microsoft Teams is only possible if your project is hosted on Azure Devops Services
So right now my project is hosted on Azure devops Server(TFS) will i able to use "Azure Pipelines with Microsoft Teams"
Azure Pipelines app for Teams only available on Azure DevOps Services currently. You could submit a user voice at website below for Azure DevOps Server:
https://developercommunity.visualstudio.com/report?space=22&entry=suggestion
Azure Pipelines with Microsoft Teams for Azure devops Server is a feature under development. Currently it is not possible.
I want to deploy my project to Azure in an App Service I have just created. Also, I created a KeyVault for all my settings.
When I try to deploy to app to the service, I have to configure the connection strings for the databases.
I click on Configure and follow the instruction and select the right app service or KeyVault. Then, in the last step, I receive this error.
Dependency configuration progress
Failed to resolve token 'ProfileResourceId'.
ErrorEmpty parameter 'resourceId'...
ErrorFailed to configure Azure AppService settings.
Failed to configure dependency Azure Key Vault secrets1
How can I fix it?
More details
I didn't follow any documentation. Usually, I use Azure DevOps to deploy application to Azure. In this case, I prefer to deploy the application from my laptop.
For that, I downloaded the publish profile from the portal and added in Visual Studio.
Then, I see some alert. At the beginning I ignored the alert but the deployed application doesn't work. So, I tried to configure each dependence.
If I press on the + to add a new service dependency, I select Azure Key Vault. Select the Azure subscription and the keyvault. Then, the local variable and review the setting. Then Finish.
In the solution I see some files for ServiceDependencies
What it is strange to me is that in the project I successful configured the Connected Services.
I had a similar issue with Application Insights. I was able to resolve by clicking "Restore service dependencies and their settings" in the Publish window.
After clicking, I was able to configure my dependencies without the "Failed to resolve token 'ProfileResourceId'." error.
I am trying to learn how to move an application from on-prem to Cloud (Azure). I have an existing application (PHP, Laravel, MySQL) which is hosted on IIS. Following this tutorial, I was able to create a VM and install LAMP stack on the VM. The last part of the article uses a Wordpress app. But I would like to use the existing custom app I have built. It resides in a repository on Azure DevOps (formerly known as VSTS).
How do I deploy my web app on to the new VM ? I still don't fully understand the infrastructure but I would to learn through this POC.
I believe you have already installed the below dependency and your VM is up and running.
Create an Ubuntu VM (the 'L' in the LAMP stack)
Open port 80 for web traffic
Install Apache, MySQL, and PHP
Verify installation and configuration
Install WordPress on the LAMP server
After this you can actually use Azure devops CI feature to deploy your custom website in the azure vm like you are doing it in on-prem.
If you have some script to deploy, you can create a Azure devops CI/CD pipeline and call the script to deploy it. It has a direct feature to deploy it from code repository.
Azure DevOps Projects presents a simplified experience where you can bring your existing code and Git repo or choose a sample application to create a continuous integration (CI) and continuous delivery (CD) pipeline to Azure.
DevOps Projects also:
Automatically creates Azure resources, such as a new Azure virtual machine (VM).
Creates and configures a release pipeline in Azure DevOps that includes a build pipeline for CI.
Sets up a release pipeline for CD.
Hope it helps.
We're working in a shared repository where we're not the owner. Our AAD accounts have been invited - username#domain.com. We have no issues accessing the Git repo.
THE ISSUE: We can't access the NuGet repo. We can access it in ADO and see all the artifacts. However, when we try to pull the repo in VS, we get a 401 Unauthorized.
The workaround is to use a personal Microsoft Account (MSA). That's understandably not a good idea - it's customer work.
THE QUESTION: Is ADO's NuGet feature only supported by MSA and not AAD accounts when the invited AAD account isn't part of the owner organization? Is this a hard limit?
Thanks!
Authentication with Azure Artifacts can be a bit of a pain... but it works (even with guest AAD accounts). I am using it like this every day. If you can download the file from the feed via the UI, you will also be able to download it via VisualStudio or other tools.
VisualStudio should have no issue at all when talking to the feed, at least if it is a somewhat current version. For VSCode and others you should try the Azure Artifacts Credential Provider and run something along these lines: dotnet restore --interactive
I have configured TFS Proxy server and have set the source control setting of my local VS client. Also TFS Application server & TFS Proxy server both are in same network Domain.
But when i am taking get latest of any team project and second time taking the get latest of same team project at different machine but files are downloading Main server and giving below warning.
TF15013: The requested Team Foundation Server is not registered with the proxy server.
Can Anyone help me out how to resolve this issue & make fast get latest.
Thanks,
You can try to use the proxy command to configure your client to use a proxy server: see Proxy Command
eg :
c:\projects>tf proxy /add http://server:8081 /default:global /collection:http://tfsserver:8080/
If that still not work, recommend you to reconfigure the Proxy, you must use service accounts to install Team Foundation Server, and Team Foundation Server Proxy. These service accounts become the identity for the installed component.
By default, every component uses a built-in account (such as Network Service) as its service account.Built-in accounts do not use passwords and already have the Log on as a service permission, making them easier to manage, especially in a domain environment. See requirements.
After that you can reference below link to configure the TFS proxy to work with Your TFS:
https://blogs.msdn.microsoft.com/buckh/2016/10/12/how-to-configure-a-tfs-proxy-to-work-with-team-services/
Update:
TFS 2013 is Xaml build system, double chick the definition will pop up the definition to edit. TFS 2017 is vNext build system, it will redirect to web client build progress page. That's by design, not related to the source settings.
And as far as I know, there isn't the utility or third part tools can open the vNext build definition in VS directly, vNext build definition is task independent, you can edit it conveniently via web portal.