I manage to use bddlib(storyq) with combination of xunit.net using resharper runner. Than decided to try to specflow, since have read its advantages over storyq.
Now I do have also another requirement to integrate this all with tfs build 2010. Am bit lost there how the big picture gonna look like. I found some articles on how to make work xunit.net with tfsbuild 2010, however there is no single word on bdd lib integration with tfsbuild more specifically continuous integration (ci).
Anyone could have helped ? thanks.
If you can run it from the command-line you can simply customize your TFS Build workflow by tossing an InvokeProcess activity in there. An example of customizing the workflow can be seen here: http://www.ewaldhofman.nl/post/2010/04/28/Customize-Team-Build-2010-e28093-Part-3-Use-more-complex-arguments.aspx
Related
I'm converting our XAML build process to vNEXT build for our on-premise TFS 2017. One step I like to automate is the create a work item task for a specific user to execute after the release has been done. Is there a built in way to do this? I have a PowerShell script but I'd prefer not to use it if there is already a better way
No, there is still no out-of-the-box feature for this. Either using the REST api or the Client Object model in a powershell script just like you have done will do the trick.
You could also take a look at this similar question: How to have TFS automatically add certain tasks to new work items?, jessehouwing has provided a great answer.
Another way is using TFS Aggregator- a serverside pugin for TFS 2013
(update 2 and later) which has the ability to create new work items
based on rules. An example task can be found here:
https://github.com/tfsaggregator/tfsaggregator/wiki/Auto-Create-Children
Update
After go through the extension in VSTS marketplace (https://marketplace.visualstudio.com/) , there is also no existing task could do this. You may still use your powershell script or write your own extension.
I've been tasked with migrating a build from TFS to VSTS, I've used TFS from a developer point of view, however I've never created builds. Can anyone give me any advice where to start, good websites, tutorials, tools that might help, anything that might catch me out etc, basically my knowledge on this is very limited so anything would help. I've no doubt there must be somebody out there who can say we've done this, here is what we did...the new VSTS build will need to be a copy of the TFS build however some analysis needs to be done as the build process is old and certain parts may not be necessary. Thanks in advance!
Migrate New Vnext build definition from TFS to VSTS
If you want to template your builds or move them from TFS to VSTS, you could also use the REST API's to perform this. Details please refer this blog: HOW TO MOVE BUILD DEFINITIONS IN TFS TO OTHER PROJECTS USING THE REST API
Another example shown here. It shows how to get the JSON response of a build definition and again using the same reference to make a new one in the project you desire.
Migrate Old XAML to New Vnext build definition from TFS to VSTS
Unfortunately, there will not be any automated conversion processes. The new builds are based on a different architecture and run on a completely different system. And you can use both the new builds and agents alongside your XAML builds, controllers, and agents.
If you have heavily customized XAML builds and custom activities, you
can continue using those builds until you are ready to port your
business logic into scripts that can run in the new builds.
You should also take a look at these series of articles by jessehouwing devoted specifically to the case like yours.
About how to create a build, you could refer this tutorial from MSDN.
FAKE documentation has description for integrating with TeamCity but there is no detailed description on TFS integration.
I think I need a custom build process template but before I create one I wanted to make sure that none exists.
Could you recommend me TFS template that integrates FAKE?
You need to create a custom activity that hosts and runs your FAKE process.
http://www.hanselman.com/blog/ExploringFAKEAnFBuildSystemForAllOfNET.aspx
There is some good documentation online for creating custom activities:
http://blogs.msdn.com/b/jimlamb/archive/2009/11/18/how-to-create-a-custom-workflow-activity-for-tfs-build-2010.aspx
And I recommend that you add it to the Community Build Tool project.
I have been using IBM Synergy tool in my earlier project for version control system.I like on of the feature which is auto propagation to child branches.
Now I am using TFS and hoping to get the same kind of feature here too but seems like its not available as could not find anything on the web on this.
I would really appreciate any help on this.
I don't believe a feature such as this exists in TFS at the moment (2013). However, there are some ALM tools that can help you propagate changes to associated branches, the 'Tfs Community Branch Tool extension'.
There are powershell modules that come with Team Foundation Power Tools you can likely cobble something together with as well, if the ALM tool doesn't work out for you. If you happen to be using TFS 2013 build you can inject a PowerShell script in your 'AfterBuild' phase to automate it, should that be something you care to do.
And as always, the TFS object model will provide you all the tools necessary to build out a TFS Build extension or MSBuild extension that would easily provide you with this functionality.
I am relatively new to MSBuild and am looking out for good resources to learn more about MSBuild and CI with TFS. Specifically I am looking out for the following specific tasks
Take latest from TFS whenever a checkin happens
Build the solution
Run the code analysis
Run Unit test cases
On success deploy the project to the drop location
Label the build
I am not looking for any reference to any books. Online resources will be good. I did google for this, but was not able to get and end-to-end tasks for this.
Any pointers in this direction will be appreciated.
Edit:
Also some good resources to custom MSBuild task will be helpful.
This is where I first started.
Edit
I don't mean to be flippant but MSDN really is a good starting place for MSBuild and most things .NET related.
In fact, everything that you describe is part of the standard TFS Build process. At least if you use MSTest for unit testing. Integration with other unit testing frameworks is also possible.
A good starting point would be MSDN, as it is quite exhaustive:
http://msdn.microsoft.com/en-us/library/ms252495.aspx
TFS2008 is very pleasant to work with in regard to Team Builds. The builds can be set up through Visual Studio itself. It was a different and a lot uglier story in TFS2005 :)
You can find a lot resources on the web if you hit any obstacles during the setup. A lot of people are using it and I never had any troubles finding blog/forum posts discussing even the most obscure issues.