Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
FubuMVC Development Group
Home
+ new post
About this group
Join this group
Message from discussion Notes from Ryan & I's conversation today about making ripple/nuget suck less down the line
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jeremy Miller  
View profile  
 More options Aug 3 2012, 10:35 am
From: Jeremy Miller <jeremydmil...@yahoo.com>
Date: Fri, 3 Aug 2012 07:35:36 -0700 (PDT)
Local: Fri, Aug 3 2012 10:35 am
Subject: Re: [fubumvc] Notes from Ryan & I's conversation today about making ripple/nuget suck less down the line
Print | View thread | Show original | Report this message | Find messages by this author

Looking at what's going on in our TC builds.  I think your strategy of
caching the nugets machine wide would be huge for fubu build times.  I'm
pulling my hair out watching how slow ripple restore is.

On Thursday, August 2, 2012 7:08:41 PM UTC-5, Matthew Smith wrote:

> +1 for mimicking Bundler

> Our modified client that Corey mentioned is also multi-threaded which
> yields faster build times and dependency updates. (We've seen this shave
> *minutes* off build times)

> We also setup a list of sources to hit in order, the last being Nuget.org.
> That order being:

> 1 - Branch specific (0-n branches)
> 2 - Internal master branch
> 3 - Internal Cache
> 4 - Nuget Official Feed

> The internal cache being a fileshare where all packages from Nuget.org are
> saved so we aren't dependent on Nuget.org servers for speed/reliability.
> We overrode the nuget.exe caching that only caches to the machine that ran
> the command. The branch specific feed is determined by the branch you are
> on when you run the command, but we also left a backdoor to configure the
> addition of another development branch in the event that you need changes
> from another project's branched packages.

> Matt


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google