[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Tools in the repository, continuous integration?

From: Lübbe Onken <luebbe.tortoisesvn_at_gmail.com>
Date: Mon, 17 Jun 2013 09:36:35 +0200

Hi Friedrich,

a CC Server would be a very cool thing indeed. I'd love to see the TSVN
build history online :)

2013/6/15 Friedrich Brunzema <brunzefb_at_yahoo.com>

> Regarding the tools:
> With our projects at work, everything that does not require an install is
> checked into a tools or library folder. This would include tools such as
> nant, nunit etc. Different projects may use different version of the
> tools, that's why we duplicate the tools in each project. As far as size
> is concerned, we have huge (4-8gb) mass-spec data files for testing - our
> internal IT had asked us not to put these files into SVN - since they don't
> change. We keep those on the network and have a nant task to synchronize
> the wc with the network.
> So I'm wondering if we can't come up with a way to have absolutely
> everything you need to setup a build environment in only two places: either
> its part of TSVN repo, or it comes from "somewhere else", but a single
> location. [Note: I don't have really strong feelings about this; the
> current approach also works]
> The build.txt file is good - we tend to have a bit less terse documents
> with screenshots in our build-guides. Developers create the build-guide,
> and an independent internal IT person follows the steps to setup the build
> machine and create the end-install CD image - just to make sure that
> nothing was missed.
> With TSVN, the build file and the instructions get peer-reviewed and
> changed when things don't work.
> We also use continuous integration using cc.net - as soon as someone
> checks something in, a build gets started, and the results are accessible
> via a web page (including the nant output). We also do automated code and
> architectural metrics and run unit tests and storytests (customer
> acceptance automated FIT tests).
> I might be able to create an Azure VM to host such an automated build
> machine as part of my MSDN benefits. I would have to check with work first
> to see if that would be allowed,a and if this would incur any further costs.
> I'm also thinking that the project needs a good unit testing framework for
> C++ that includes a visual test runner. On the .net side, nUnit is pretty
> nice and a test runner is part of the resharper plugin for VS we use. Any
> suggestions for the best one to use? Even though there is a lot of UI in
> TSVN, it is still possible to structure things in such a way to test the
> "view-model" logic automatically. Stefan said there are some unit-tests
> for the Async stuff already - I have yet to take a look.
> Best,
> Friedrich

- Lübbe
Please help me get more space on Dropbox :)
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-06-17 09:36:40 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.