I've installed Azure Devops Server 2019 on my local server. Now I want to setup a agent pool. To do this, the I've to follow instructions in the image below.
As here, I just downloaded the zip file an ran the config.cmd file, in the first step, it requires Server Url which as I searched over the net, people enter the Organization Url there.
The problem is I have no organization in my local Azure Devops! and when I click on the logo, It redirects me to project collection page:
What should I enter as Server Url in configuring Agent pool?
Agree with bryanbcook,
We can check the doc and switch the doc version to Azure DevOps Server 2019 to check the Server Url, it should be https://{your_server}/tfs
You can refer to this doc to configure the self-hosted agent.
Azure DevOps Services, which are hosted in the cloud, and Azure DevOps Sever 20XX use slightly different terminology. The term “Organization” and “Project Collection” refer to the same thing.
Related
what I did;
I have my c# windows form application on Azure Repo and I created a build.
I assigned my physical test server to Azure DevOps under the Deployment groups page. And it is online.
I defined a release, I added an artifact that refers to the build pipeline from the Azure repo.
Now I want to transfer my windows form app release files to my physical test server (windows) under the Desktop folder and run. (also stop and delete previous app if it is already running)
For that, I tried to add a stage. But for the stage templates, I don't know which one to choose. There are deployment options for IIS and Azure services.
Bufre, I published my ASP.NET app using IIS website deployment. Worked fine. But how to do it for a desktop application? How to transfer and run?
I see a as a similar issue here, But I am new to YAML files and I could not produce.
Where to mention target physical path, which template to choose? Could you please advise on the steps?
You must install the DevOps agent on this server, then add it to the agent pool and then use any task that allows to install your app (depends on what kind of app you have). All tasks will be executed on the server directly, so you can use PowerShell, cmd or what ever.
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/pools-queues?view=azure-devops&tabs=yaml%2Cbrowser
We are using Azure Devops 2019 (App and data tiers are on different servers),We have done a domain migration due to which we had to change Devops URL from https:\Devops.OldDomain.com to https:\Devops.NewDomain.com
Below are the steps followed
Changed URL on IIS Devops Site and applied a third party certificate for https ( made sure certificates are added to trusted Root Cert)
Changed Public URL (changed the url to new Devops Url) from Devops admin console ( verified the access point from tbl_AccessMapping and updated it to new url)
Restarted the Devops server
Below are the issues identified
1)I have noticed build agents stopped working\offline and when I try to setup new agents, I see below
"An error occurred while sending the request.Failed to connect. Try again or ctrl-c to quit"
tried changing agent file to correct url (yet no luck)
2)When I launch Azure devops admin console I see below error
When I try to add Devops url from visual studio (Visual studio is installed inside Devops server) I see below error
"TF400324:Azure Devops services are not available from server, The underlying connection was closed"
Am I missing anything? I understand that some communication is missing between Application and Data tire, but I could not identify whats going wrong
Try to clear the following caches:
Clear TFS caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache
Delete the contents of the Cache directory, including all subfolders.
Regarding VS, close all Visual Studio instances, delete %LOCALAPPDATA%.IdentityService.
Reset IIS by pressing Win+R, and input iisreset in the Run.
I have the following problem to solve but I cannot find the right documentation.
I just upgrade the version control software from TFS (on premise) to Azure Devops Service.
I have my own self-hosted building agents that are hooked upo with the TFS istance.
What I want to do now is to redirect them from pointing to TFS to pointing into Azure Devops Service.
I can find everything about the authentication part, token and so on but I miss the basic steps on reconfiguring the building agents themselves. Can someone help me by any chance?
You can reconfigure your build agents into Azure DevOps. Remove and re-configure an agent
To remove the agent:
.\config remove
After you've removed the agent, you can configure it again.
I am planning to setup sonar in VSTS for that I tried searching blogs and stack overflow.I got few links to setup sonar but all I need is to have Microsoft SQL windows server 2012 R2 as a IAAS. I need dedicated VM as IAAS(Infrastructure as a service) to configure sonar in Azure after creating Microsoft SQL server VM I can give that endpoint in VSTS and can run sonar.But in my company we are having all VM's as a PAAS(Platform as a service).My organization is not ready to have VM as IAAS.So kindly provide the solution how can I configure sonar in VSTS.
The below link received from stackOverflow.
http://donovanbrown.com/post/how-to-setup-a-sonarqube-server-in-azure
SonarQube is designed to use a dedicated server and needs access to a database. Take a look at the system requirements for details. There is no way to host it inside of VSTS.
If your organization isn't ready to do IaaS with Azure, then you have two options. The first option is to setup a SonarQube server in your office or data center and make it publicly accessible.
If that isn't an option, then your only other option is to make use of SonarCloud as Fabrice mentioned in the comments. Take a look at this blog post for setting up VSTS and SonarCloud.
Well, if you wish to hosted in SonarQube in Azure then you are in luck. You can make a VSTS/Azure DevOps Project where you add this Github: ARM Template for VM, network and DB setup for SonarQube to your a GIT repo.
This will give you the possiblity to have you secrets safe in VSTS/Azure Dev but automatically support the SonarQube setup from Azure DevOps with Cloud Infrastructure.
I am developing CD release pipeline using TFS 2015 update 2 on-prem instance. I'm relying on ARM template to setup Azure website and Azure Sql server. I'm using FTP method for deploying website bits from internal Build server to Azure website. For this website deployment I'm reading the credentials from PublsihingProfile of the newly created website.
Is this a right way or can you suggest a better way? Any comments are appreciated.
P.S. Customer wants to use FTP method and not WebDeploy.
If you really have to use FTP, and the thing you're not happy with is the process/password secret management, you could try this:
https://marketplace.visualstudio.com/items?itemName=januskamphansen.ftpupload-task
Its a VSTS extension task for release, which works with the vnext build/release system in VSTS or TFS2015 server. This task lets you put the parameters in against each environment you setup, and mark the passwords as secrets so they wont come out in logs or the UI.
The step basically wraps up the process of doing the ftp bit for you - you may want to do other steps as part of the release.