Re: [dotNetRDF-Develop] TeamCity for dotNetRDF revisit

[Rob V. <rv...@do...>]

Hey Tom

Yes we've gone around on this a couple of times before and I have never
had the free time to look into it further.  If you have the capacity to
set up TeamCity to run builds and testing that would be great.

If you want to explore moving to NUnit that is fine provided you do it in
a separate branch/fork for the time being.  Now the remaining blocker bug
you had open (graph equality) is solved I want to go ahead and run
regressions and then hopefully push out 1.0.0 towards the end of the week
(unless you have any objections?) so anything that interferes with that is
bad for me right now!

For me the deal breaker is being able to Debug tests inside of Visual
Studio without having to jump through additional hoops (i.e. Debug >
Attach to Process) as NUnit straight out the box seems to require.  To be
honest even if JetBrains won't give us an open source ReSharper license I
can easily afford to buy a personal license since I imagine it is
primarily me who spends a lot of time running tests in Debug mode.

I'll start a separate thread on NuGet publishing

Rob

On 4/13/13 3:23 AM, "Tomasz Pluskiewicz" <tom...@gm...>
wrote:

>Hi Rob
>
>Some time we discussed setting up continous integration for dotNetRDF.
>I am upgrading my VPS to a more powerful machine and I have already
>set up TeamCity. It will also be possible to install some triplestores
>for integration testing.
>
>However I'm hitting a wall with unit tests because you use MSTest.
>Would you be fine with me converting to NUnit? That way TeamCity will
>run without installing Visual Studio and VS Express users will also be
>able to build the whole solution. Also I think we could ask JetBrains
>for ReSharper licence for our project (in case you would ask about
>running the test suite from within VS). Oh and by the way, with the
>introduction of NUnit there can be a lot less code for similar tests,
>which can be parametrized. I assume you know the TestCase attribute.
>
>When TeamCity builds are running I think we should also automate NuGet
>publishing. For that some changes will be needed to have automatic
>version numbering. Also you would have to explain how you nuget pack
>dotNetRDF. In a separate email maybe.
>
>Also I thought that maybe there could be two flavors of those
>packages. One as usual for stable builds and a new one, which would
>publish automatically for each successful build. What do you think?
>
>A thing to consider here is moving to a dedicated branch for release
>development and leaving default only for bugfixes.
>
>Any thoughs?
>
>Thanks
>Tom
>
>--------------------------------------------------------------------------
>----
>Precog is a next-generation analytics platform capable of advanced
>analytics on semi-structured data. The platform includes APIs for building
>apps and a phenomenal toolset for data science. Developers can use
>our toolset for easy data analysis & visualization. Get a free account!
>http://www2.precog.com/precogplatform/slashdotnewsletter
>_______________________________________________
>dotNetRDF-develop mailing list
>dot...@li...
>https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop