Opened this query in MS Developer Community Forum / Azure DevOps issue
https://developercommunity.visualstudio.com/t/No-agent-found-in-pool-Default-which-sat/10141890?space=21&q=gtversion&entry=problem
Trying to work out why the "Pipeline" runs successfully with my self-hosted docker agent but the "Release Pipeline" fails, it's asking for a version way under the version of the agent I am running
“No agent found in pool Default which satisfies the specified demands: azureps, Agent.Version -gtVersion 2.144.0”
Any given help will be very much appreciated
Compromised installing the PS AzureRM module necessary for the release pipeline tasks to run, and added two user-defined capabilities to the agent to overcome the initial error
Documented the "solution" here
https://developercommunity.visualstudio.com/t/No-agent-found-in-pool-Default-which-sat/10141890
Related
I am trying to create CI/CD pipeline in azure databricks with azure devops using a windows self hosted agent. I am following this blog: https://www.linkedin.com/pulse/ci-cd-azure-databricks-using-devops-deepak-rajak I am getting this error and I am not able to resolve it any idea how can I resolve this?
Looks like you're hitting a known issue. Make sure the most recent version of the Azure CLI ir installed and available on the %path% for the user that runs the Azure Pipelines agent.
I have yaml pipeline in Azure Devops. Simple tasks such as building a project and running unit tests are taking 10 times longer today than they were. I'm in Europe and I can see that the Artifacts service is degraded. Would this explain the slow build and does anyone know a work-around such as a way to force the build agent to run in a different region?
https://status.dev.azure.com/
The issue seems is related to the following Azure DevOps Incidents:
https://status.dev.azure.com/_event/233282345
https://status.dev.azure.com/_event/233249026
https://status.dev.azure.com/_event/233260207
Please try as the workaround mentioned in the Incident, adding the self-hosted agents to run your pipelines.
Now all regions have the problem with pipelines:
As our SonarQube instance was not accessible over internet, I am getting the below error in "Prepare analysis on SonarQube" task during the analysis of a java project.
[SQ] API GET '/api/server/version' failed, error was: {"code":"ENOTFOUND","errno":"ENOTFOUND","syscall":"getaddrinfo","hostname":"ABC.XYZ.com","host":"ABC.XYZ.com","port":443}
Some links suggests that by adding proxy variable will solve this issue. But don't know how to do it. Some links suggests to install agent service (from Deployment Pool section) will solve this issue. In that case we need to do it for multiple organization.
So anyone please let me know what will be the proper solution for this issue.
For this problem when using SonarQube on Azure DevOps Services (VSTS), installing self-hosted agents generally is a better way to solve the problem.
To install self-hosted agents on multiple organizations, you can try to set up a shell script that executing the installation command lines in a loop to install a self-hosted agent for each organization.
When using Azure DevOps I notice that occasionally my pull request builds will fail. After some tracking down I noticed that this is only happening when another build is already running.
It seems that the reason is that the files in the output for the build (exe, dll, note_modules, etc.) will be locked so when another build is started the new build will fail until the currently running one is finished, then I will have to manually re-queue the build again.
I am not very familiar with Azure DevOps pipelines since we recently migrated to this platform and also not sure of the best way to fix this issue. The sln's being built include .NET Framework, .NET Core, TypeScript, and Node.js if that helps at all.
I would love to post the logs and current configuration, but due to company policy I'm not allowed to... :(
Azure DevOps build pipelines fail when another build is already running
You could try to use/add a Capability, like Agent.Name to that two specific build agents then in the build definition you put that capability as a Demands.
As stated here:
How to send TFS build to a specific agent or server
The Capabilities of the agent:
Project Settings->Agent pools->Your agent pool-> Agents->Agent->Capabilities
The Demands of the build pipeline:
Options-> Demands:
In this case, when a pipeline is running in this particular agent, another new build will be in pending state until the current build is completed.
Normal VSO release should work with the 'Azure Pipelines' agent. But it is failing in Azure Powershell task saying 'Could not find the modules: 'Az.Accounts'.. While same task is running with the 'Fortify' agent
Tried all possible agents other than 'Fortify'. Didn't work.
I had the same problem with version 4 of the task. I switched to 3 and it got fixed.
I came across a similar error using task Azure Powershell "Could not find the modules: 'Az.Accounts' with Version: '5.1.1' If the module was recently installed, retry after restarting the Azure Pipelines task agent".
My fix to this error is to use the latest version of azurePowerShellVersion,
azurePowerShellVersion: 'latestVersion'
For classic view:
select the latest version 4.* of task Azure Powershell
check latest installed verison for azure powershell version
If above fix does not work for you. For better troubleshooting, please post the full error message and the detailed settings of Azure Powershell task.