We currently make use of the Tfs SonarQube extension (version 3.1.0) on an onprem Tfs2015.Update3 (14.102.25423.0)
We use the following sonar tasks in our build definitions:
Prepare the SonarQube analysis
Complete the SonarQube analysis
These all work fine.
I have now upgraded the Tfs server to Tfs2018 (version 16.122.27102.1).
To my (pleasant:- ) surprise the SonarQube extension (version 3.1.0) still works!
When I however read this link on the sonarqube site, it seems like versions 3.x should NOT be compatible with Tfs 2018.
https://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Extension+for+VSTS-TFS
Versions 3.x are compatible with:
TFS 2015 Update 3
TFS 2017 Update 1
VSTS
Versions 4.x are compatible with:
TFS 2017 Update 2+
TFS 2018
VSTS
Am I missing something here?
Thanks!
The compatibility "matrix" on the VSTS/TFS documentation gives the recommended setup - i.e. what has been tested and will work for sure.
In other words, versions 3.X might be forward compatible with recent versions of TFS - but this compatibility is not tested and will probably (even certainly) be broken some day in the future.
This is why this is a very good suggestion to move to the recommended versions (here 4.x for a TS 2018+) so that:
your setup does not get broken without notice when upgrading your TFS
you benefit from all the latest new features and improvements that won't be backported to the 3.x versions.
Related
I am not able to determine, which version of the SpecFlow Visual Studio plugin I need to run the old version 2.2.0 of SpecFlow
Due to administrative constraints, we cannot use any other SpecFlow version than 2.2.0
I have tried several older versions of the VS plugin, but with my existing Code (based on SpecFlow 2.2.0), all these result in the error:
Error CS1029 #error: 'Version conflict - SpecFlow Visual Studio extension
attempted to use SpecFlow code-behind
generator 1.9, but project 'XXXXXXX' references SpecFlow 2.2.'
I suppose that I need some plugin Version, that works internally with 2.2
I cannot use the SpecFlow.Tools.MsBuild.Generation package, as this is not yet supported with 2.2.0.
Anyone can help me out? The release history of the SpecFlow Visual Studio Plugins can be found here:
https://github.com/techtalk/SpecFlow.VisualStudio/releases
EDIT
I use Visual Studio 2017 (15.9.6)
In the "packages" folder there are SpecFlow-2.2.0 and SpecFlow.MsTest-2.2.0. I deleted them, I deleted the nuget package Cache and rebuild the solution.
Problem still exists.
The error you are seeing has nothing to do with the suggestions in the comments. It is an additional check we added to the extension.
For SpecFlow 2.2 you have to use an older version of the extension. You can find them at https://github.com/techtalk/SpecFlow.VisualStudio/releases
When I am remembering correctly v2017.2.7 should work for it.
Don't forget to turn off automatic updates of the extension. If you do, you will get again the latest version.
Blog post about how to do it is here: https://specflow.org/2018/vs-integration-breaking-changes-affects-all-users/
Full disclosure: I am one of the SpecFlow and SpecFlow+ developers.
make sure you install the right Specflow extension for your VS(try uninstall and reinstall as well) also make sure you set "Enable SpecflowSingleFileGenerator to false" in VS>Tools>Options>Specflow. you only need this to be true for version 3 onward I suppose.
I had this issue, and while It worked to some extend however, I just install VS 2015 and use specflow 2.2 under that. you should be able to make it work for VS 17 I guess.
On TFS 2015, I upgraded from 3.0.0 to 4.0.1, however the new 4.0 tasks are not showing up in the tasks list.
When I try to reinstall 4.0, I get confirmation that it is already installed:
Shows version is already installed
However the new 4.0 related tasks are now showing up in the tasks list
I do still see the version 3.0 tasks
Is 4.0.1 compatible with TFS 2015? How do I get the 4.0 tasks to show up in the tasks list?
In TFS 2018, a new installation of 4.0 works just fine:
4.0 Tasks Showing Up in TFS2018 after initial installation
Thanks in advance for the feedback.
You are facing the following bug: VSTS-135
TL;DR: version 4 of the extension uses a mechanism that is available only starting with TFS 2017 Update 2.
I am wondering if Borland StarTeam 2008 Release R2 can be integrated with Jenkins. Or do i need to upgrade StarTeam. If yes, please let me know where can i find the integration instructions. Thank you.
Borland developed a StarTeam plugin for Jenkins back in 2007. Until 2013, the plugin was community-maintained, so you can find the source code in GitHub and the .hpi files in Jenkins plugins page. Probably most of those versions will work seamlessly with StarTeam 2008 R2.
Since version 0.7.2, released in June 2015, they decided to rewrite the plugin and newer versions only work with StarTeam 14.4 or later.
I am using specflow for BDD for a POC project. I had installed the nuget packages for Specflow ,Specflow.NUnit, NUnitTestAdapter and NUnit (version 2.6). I seemed to be happy since i was getting the expected result.
After a few days, I am working on a new project and i installed all the nuget packages mentioned above. Everything worked fine again. However, when i upgraded Nunit from version 2.6 to the latest stable version 3.0, my tests were not discovered in the Test explorer.
I can continue with the older version but still i would like to go with the latest stable version
I am not sure what steps do i need to take to get my specs running and see all my tests in the Test Explorer.
Any help would be appreciated.
Thanks.
The current version of specflow at time of writing (1.9) won't work with nunit 3. The new version, currently under development (v2) will support it so you will need to wait for that to use nunit v3, or use the beta version from the CI build
I have upgraded my project that hast the Build Template to use 2012 (11.00 assemblies) and upgraded it to use .NET framework 4.5. I have also upgraded the Custom Activities project to use version 4.5 framework and use 11.00 assemblies.
I have several questions regarding this can i use this upgraded template with TFS 2010? At the moment our server which has TFS 2010 installed hasn't been upgraded to TFS 2012.
Also the custom activities that I use in the upgraded template, they look grey. Is this normal?
Custom Activities should match with the version of Team Foundation Build Services. As you are using TFS 2010 build services, it will throw errors for the custom activities compiled with 11.0 version.