I follow SonarQube documentation:
But with TFS2015 express I don't see build step "SonarQube for MSBuild". Is that some plugin to install into TFS express ? Or the feature is not allowed to Express edition ?
This build step is RTM with TFS 2015 update1. Details please refer Team Foundation Server 2015 Update 1
SonarQube build tasks that embed the sonar-msbuild-runner 1.0 work
with on-premises and hosted agents. You can now use two build tasks to
execute a SonarQube analysis in conjunction with MSBuild. Before the
build steps that execute the actual MSBuild, insert a SonarQube for
MSBuild - Begin Analysis task to specify the SonarQube project
parameters, the connection to the SonarQube server, and (until
SonarQube 5.2 is available) the connection to the SonarQube database.
After the build and any test tasks, append a SonarQube for MSBuild -
End Analysis task to complete the analysis and send the data to
SonarQube.
So, the feature is also not in TFS Express 2015. There is no TFS Express 2015 upade1 for now. If you want to use this feature, you may have to use either TFS2015 update1 or VS Team Service.
Related
I currently manage a TFS 2018.2 TFS server for 100 users that have Visual Studio Enterprise. On our build and release resource limits tab we show that we have 103 release pipelines.
I am acquiring the management of another TFS 2018.3 server, but the users only have Visual Studio Professional. As such their release pipelines are limited to 1 pipeline.
I have read the page at: https://blogs.msdn.microsoft.com/tfssetup/2017/11/14/understanding-build-and-release-pipelines-visual-studio-team-servicesteam-foundation-server/
From that information I believe what I am reading is that this number only affects Releases running in the TFS Release pipeline, and not build running in the build pipeline. #1 : Did I interpret this correctly?
Second, we are considering upgrading our server to Azure DevOps Server 2019. On this page: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops-2019&tabs=browser
There is an important note stating as follows:
Starting with Azure DevOps Server 2019, you do not have to pay for self-hosted concurrent jobs in releases. You are only limited by the number of agents that you have.
Therefore, if we do upgrade to the on-premises version of TFS Server, we can run all of both builds and releases currcurrently for which we have agents installed. #2 : Can you confirm this is also correct?
I tested and confirm your interpretation for the documents in above links is correct.
With TFS, you only need pipelines for deploying releases; no pipelines are required for builds since unlimited concurrent builds are included with the TFS server license.
I tested on tfs2018 multiple build pipelines could run concurrently based on how many on-premise agents I have installed. But i can only run one release once a time.
Starting with Azure DevOps Server 2019, you do not have to pay for self-hosted concurrent jobs in releases. You are only limited by the number of agents that you have.
I also tested on vsts2109, both build and release pipeline can concurrently based on how many on-premise agents I installed.
The SonarQube docs specify:
When analysis is triggered from a Pull Request the SonarQube Scanner for MSBuild - End Analysis task decorates the updated source code in the Pull Request with the new code quality issues, instead of pushing the analysis report to the SonarQube server.
How can you turn this on? We are using TFS 2018 with version 3.x of the SonarQube TFS/VSTS extension.
The SonarQube for MSBuild - End Analysis task is deprecated now and it can not be used.
The workaround is execute SonarQube.Scanner.MSBuild.exe end command manually.
You can queue your build by the private agent which installs SonarQube Scanner for MSBuild.
We are using TFS 2015 and we are trying to run build definition on a remote server with a test agent.
TFS complains that our test agent version is too old:
No agent found in pool 1 which satisfies the specified demands:
Agent.Version -gtVersion 1.94.0
The question is: how can you tell the current version of the agent?
You can see it on the Agent pools pagein TFS under Capabilities.
I am doing continious Integration between TFS and Jenkins.I am using TFS as a repository server.I am able to create workspace from TFS in jenkins and building of application successfully.I need automation build after TFS checkin.
IIRC Jenkins polls tfs to see if there's been a checkin, when there has it does a build (as opposed to TFS kicking off the build).
We use Jenkins as our CI build server but have moved over to TFS to do all the project management stuff (user stories, dev tasks, test cases, reporting, automation). How do I setup TFS2010 to use our Jenkins build server?
it's actually more like the other way around. You need to configure the TFS plugin for Jenkins, telling it to use TFS as your source control system. below is a link to the jenkins TFS plug-in...
https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin