Tabspace nant target

[Friedrich Brunzema]

Hi,

I propose to write a nant target for running tabspace. I will put Stefan's tabspace tool into my tools folder - could we put it into the general tools: http://code.google.com/p/tortoisesvn/downloads/list?

Both the 64 and 32 bit versions should be put in, and the script can decide which one to use.

Let me know what you think.

Friedrich

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058032

To unsubscribe from this discussion, e-mail: [dev-uns...@tortoisesvn.tigris.org].

[Stefan Küng]

On 14.06.2013 01:23, Friedrich Brunzema wrote:
> Hi,
>
> I propose to write a nant target for running tabspace. I will put
> Stefan's tabspace tool into my tools folder - could we put it into
> the general tools:
> http://code.google.com/p/tortoisesvn/downloads/list?
>
> Both the 64 and 32 bit versions should be put in, and the script can
> decide which one to use.

That's a good idea.

I was wondering: I know we didn't add the tools to our repository before
because people were concerned about the bandwidth it would require to
check out the TSVN sourcecode. But that was years ago. By now I think
bandwidth isn't that much of an issue anymore.
So how about adding the whole tools directly in /trunk/tools? That way
we wouldn't have to tell people to download them when building TSVN.

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058084

[Friedrich Brunzema]

Stefan wrote:

>I was wondering: I know we didn't add the tools to our repository before
>because people were concerned about the bandwidth it would require to
>check out the TSVN sourcecode. But that was years ago. By now I think
>bandwidth isn't that much of an issue anymore.
>So how about adding the whole tools directly in /trunk/tools? That way
>we wouldn't have to tell people to download them when building TSVN.

Yes, do it! -- The build guide would need updating then.

Friedrich

[Stefan Küng]

On second thought:
the tools folder would be bigger than the src folder or all external
libs together.

I just update the tools.7z file on the download page to the latest
versions and leave it that way.

Stefan

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------

http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058106

[Stefan Küng]

On 14.06.2013 01:23, Friedrich Brunzema wrote:

> Hi,
>
> I propose to write a nant target for running tabspace. I will put Stefan's tabspace tool into my tools folder - could we put it into the general tools: http://code.google.com/p/tortoisesvn/downloads/list?
>
> Both the 64 and 32 bit versions should be put in, and the script can decide which one to use.
>
> Let me know what you think.

Added the NAnt task in r24383

--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net

------------------------------------------------------

http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058111

[Oto BREZINA]

On 2013-06-14 22:30, Stefan Küng wrote:
> On 14.06.2013 18:09, Friedrich Brunzema wrote:
>> Stefan wrote:
>> >I was wondering: I know we didn't add the tools to our repository before
>> >because people were concerned about the bandwidth it would require to
>> >check out the TSVN sourcecode. But that was years ago. By now I think
>> >bandwidth isn't that much of an issue anymore.
>> >So how about adding the whole tools directly in /trunk/tools? That way
>> >we wouldn't have to tell people to download them when building TSVN.
>>
>> Yes, do it! -- The build guide would need updating then.
> On second thought:
> the tools folder would be bigger than the src folder or all external
> libs together.
>
> I just update the tools.7z file on the download page to the latest
> versions and leave it that way.

If you put zip instead of 7z you remove one depency, but that's not what
I want write about.

You may add Nant to repository and even you will not get and unzip
target can take care of download and "install"
>
> Stefan
Oto

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3058159

[Friedrich Brunzema]

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 Onken]

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 <brun...@yahoo.com>

--
Cheers
- Lübbe

--
Please help me get more space on Dropbox :)
https://www.dropbox.com/referrals/NTIwMzcxNjI5

       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN

   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB

[Lübbe Onken]

How about adding a NAnt target like "NAnt init" or "NAnt config", that would pull in the tools file(s) via http from a defined location and unpack them in the tools folder?

I deliberately wrote file(s), because some people might only want to build either docs or the executables and they wouldn't need the entire set of tools.

"NAnt config" could also try to find the paths to the other tools (VS etc.) and set the variables in default.build.user accordingly.

Cheers
- Lübbe

--
Please help me get more space on Dropbox :)
https://www.dropbox.com/referrals/NTIwMzcxNjI5

       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN