I have just updated the SonarQube plugin to V4 in my VS2017 VNext build but the build is sat waiting for an available agent.
All my agents have MSBuild and Java, are there any other capabilities required for the V4 update.
If I move back to the V3 SonarQube plugin the same build works fines
v4 of the tasks do not add any new demands. However, the new version is written in Node.js rather than PowerShell (so it can run on non-Windows build agents). If you are running an on-premise version of TFS you might need to update your build agents.
FYI when I ran the v4 of the task on TFS2017.2 the build failed with the message No agent found in pool X which satisfies the specified demands: .... Agent.Version -gtVersion 2.119.1
The Microsoft docs for upgrading the agents are here. I ended up downloading the specified version of the agent from the vsts-agents releases page on GitHub.
Related
I have a Xamarin project that builds just fine on my local machine but is not building on the azure server. Anyone see this before ?
##[error]The nuget command failed with exit code(1) and error(NU1201: Project XXX.XXXX.XXXXX is not compatible with monoandroid10.0 (MonoAndroid,Version=v10.0). Project XXX.XXXX.XXXXX supports: netstandard2.1 (.NETStandard,Version=v2.1)
Upgrade your nuget version to 5.8 and this will all go away :)
If you use Azure pipelines to Build and deploy Xamarin apps, please refer to this doc. And if you use Microsoft-hosted agent, its build environment is different from local machine, such as it may lack of some software or installs different software version. You can see the installed software for each hosted agent by choosing the Included Software link in the table.
To your issue, please check which NuGet version do you use to build this project locally, and then use the NuGet Tool Installer task in Azure pipeline to specify this NuGet version(maybe 5.8.0 works for your issue as Mouse commented) to build your project with Microsoft-hosted agent.
Also you could deploy local self-hosted Windows agent and use it in Azure pipeline to build your project, which will run local build environment.
BTW, you could refer to this doc: Review logs to diagnose pipeline issues to make initial troubleshooting steps when encounter pipeline issues.
I have a TFS server on a remote machine, and succesfully installed a build agent on my own machine. The connection between these works as intended:
The agent is online, and running succesfully. However, when I try to queue a build, I get this error:
I think the solution lies in this text:
No agent found in pool Default which satisfies the specified demands:
msbuild
visualstudio
DotNetFramework
Agent.Version -gtVersion 1.98.1
Since I have MSBuild, VS2017 and .Net installed on my machine, I think it's the Agent.Version that's causing problems. But how do I check what version of the agent I have running? I followed this guide to installing the build agent. And where can I find other versions of the build agent online? The MS site doesn't seem to offer download options for older/newer versions of the build agent.
If you installed the agent according your link so the version should be fine (because you downloaded the agent from your TFS).
Go to Agent Pools page, then check the agent's Capabilities.
Look after the the version of MSBuild/VS/.Net, maybe on the agent computer the right version not installed.
Another option - the agent didn't recognize the installed stuff so you can add it to the agent's capabilities manually by click on "Add capability":
I had a similar issue after upgrading Azure DevOps On Premise from 2019 RC2 to 2019 Release. After the upgrade I had to download the new Build Agent from the Azure server and install the new version on my build agents. After upgrading the build agents they began reporting the correct capabilities.
one of our feature teams who is using SonarQube since long and they are now getting issues when they upgrade to VS 2017,To support SonarQube for scanning in VSTS build, we need the task updated with SonarQube 2.3 or higher to support along with VS 2017 for code analysis. May I know is there any work going on this when can we get the support for VS 2017?
Regarding SonarQube extension in VSTS, you can install SonarQube 3.0.2 version. (You need to update SonarQube extension if old version has already been installed in manage/admin extension page of you VSTS. https://XXX.visualstudio.com/_admin/_extensions)
After that, you can change 3.* version of SonarQube Scanner for MSBuild task in build or release.
I have installed the SonarQube extension in VSTS, configured it with my SonarQube server, username, and token, and created a task to perform a sonarqube cli analysis. However, when I get to the task in my build, I get the error message that it is not compatible with my operating system. Is this due to my build agent being Linux? Is there a way to get the SonarQube cli extension to use the SonarQube scanner for Linux rather than SonarQube scanner for windows?
The incompatibility is indeed that you're trying to analyze .NET from Linux. The SonarQube Scanners are not yet compatible with that combination.
I'm trying to set up continuous integration at my current place of work. It's not something I've done before so I'm fairly certain that there will be a few steps I've not done or things I'm un-aware of.
I installed TeamCity Professional 7.1.3 on a build server (Windows Server 2008 R2). I've created a simple .NET application that has no database connections and only three NUnit tests. This app uses .NET framework 4.
I set up a build step using NUnit and received a number of errors but I've now resolved them, basically by installing the .NET framework on the build server.
I'm now adding an extra step using Visual Studio but TeamCity now displays the warning 'No enabled compatible agents for this build configuration'.
This question looks similar to mine:
What do I need to install a Visual Studio 2010 (sln)-compatible Build Agent in TeamCity? and it helped me solve the problems I had with NUnit but not for this current problem.
Is there something I've missed during my set-up? If I'm building and running tests with NUnit do I need to bother with this second step?
You installed the full framework, correct -- not just the client pieces? Here's a TeamCity forum post on how to resolve the Unmet requirements:DotNetFramework4.0_x86 exists compatibility error when you've previously installed the framework.