Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Incremental build with NCrunch console?
GreenMoose
#1 Posted : Monday, January 7, 2019 2:04:00 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 424

Thanks: 107 times
Was thanked: 49 time(s) in 48 post(s)
[NCrunch Console Tool v3.23.0.9]

Is there a way to som sort of "incremental build" behavior with NCrunch console in order to avoid cleaning workspace after every run, and if not are there any plans for it?

Background
Currently I reuse NCrunch cache (-NCrunchCacheStoragePath) for every build on TeamCity, and NCrunch cleans workspaces after it is done executing.
Since I use impacted tests only, the build/analyse phase takes a long time since NCrunch re-compiles every time.
Example of where build /analyze phase vs test run phase:
Build/Analyse vs test run

Thanks.
Remco
#2 Posted : Monday, January 7, 2019 10:04:37 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 5,500

Thanks: 723 times
Was thanked: 909 time(s) in 865 post(s)
Hi, thanks for posting.

Right now, there is no way to avoid cleaning up the workspaces at the end of the run with the console tool.

Since it's basically just a headless client, it has more or less the same bootstrap sequence and follows the same execution pattern (load, build workspaces, build projects, analyse them, run tests, clean everything up, terminate).

It would be advantageous for the console tool to preserve workspaces between sessions, or even to not use them at all, since concurrent changes to the foreground solution aren't usually a problem.

This is one of the things that has become more clear as we've continued to develop the tool: The original scope for the console tool was for a headless client, when actually it seems what was needed is a parallel test runner that can work inside a CI system. There's a whole lot of complexity inside the NCrunch engine that adds no real value to the console tool and generally just takes up time/CPU.

One of the problems we're facing at the moment is that the console tool was only really intended as a side feature, but it's become a bit of a monster on its own. We spent a considerable amount of time last year to bring it up to a more useful level. This is happening at the expense of the core product itself (which for the sake of revenue, is actually the important one). So in the near term, I don't see us doing much more on the console tool beyond basic operational fixes. The long term is less clear.

You're welcome to track this one on uservoice if you like so that it doesn't get lost. I don't think it's been requested yet.
GreenMoose
#3 Posted : Tuesday, January 8, 2019 9:13:20 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/17/2012(UTC)
Posts: 424

Thanks: 107 times
Was thanked: 49 time(s) in 48 post(s)
Yeah focusing on NCrunch for VStudio sounds like the right thing to do.

Still, I will have my hope for an "incremental build light" feature as in -PersistentWorkspacePath option or similar would make implementation easy enough to make it in a release in a not too distant future :)

Request created: https://ncrunch.uservoic...-build-for-console-tool

Thanks.
1 user thanked GreenMoose for this useful post.
Remco on 1/8/2019(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.027 seconds.