Nuget build server integration opinions

Apr 8, 2011 at 3:14 PM

I have read the many discussion concerning the integration with build servers. I read the post http://blog.davidebbo.com/2011/03/using-nuget-without-committing-packages.html concerning Nuget without committing packages and then using the command line utility in the Pre-Build event. I am trying to get opinions from others as to how they are incorporating Nuget packages/dependencies and using internal Nuget servers in their dev shops? One of my concerns would be that a failed build would occur if a package could not be retrieved. I guess now that things are getting more and more stable with this project I am looking for a best practice guide to implementing Nuget in a large dev shop situation. Any pointers or links to articles or opinions would be greatly appreciated as most of the articles out there right now are intro to using Nuget and the few discussions I found on this board seem to be the how-to to get it to work. Now all I need to do is start off on the right foot.

Apr 8, 2011 at 3:23 PM
I use a Rake script that gets all the packages before building, testing etc.

The CI server calls the tasks in the script.

If you are concern about network availability, maybe you should
install a local repository with all the packages you need to avoid
that.

Any questions let me know.

On Fri, Apr 8, 2011 at 10:14 AM, madhatter84gn
<notifications@codeplex.com> wrote:
> From: madhatter84gn
>
> I have read the many discussion concerning the integration with build
> servers. I read the post
> http://blog.davidebbo.com/2011/03/using-nuget-without-committing-packages.html concerning
> Nuget without committing packages and then using the command line utility in
> the Pre-Build event. I am trying to get opinions from others as to how they
> are incorporating Nuget packages/dependencies and using internal Nuget
> servers in their dev shops? One of my concerns would be that a failed build
> would occur if a package could not be retrieved. I guess now that things are
> getting more and more stable with this project I am looking for a best
> practice guide to implementing Nuget in a large dev shop situation. Any
> pointers or links to articles or opinions would be greatly appreciated as
> most of the articles out there right now are intro to using Nuget and the
> few discussions I found on this board seem to be the how-to to get it to
> work. Now all I need to do is start off on the right foot.
>
> Read the full discussion online.
>
> To add a post to this discussion, reply to this email
> ([email removed])
>
> To start a new discussion for this project, email
> [email removed]
>
> You are receiving this email because you subscribed to this discussion on
> CodePlex. You can unsubscribe or change your settings on codePlex.com.
>
> Please note: Images and attachments will be removed from emails. Any posts
> to this discussion will also be available online at codeplex.com
Apr 17, 2011 at 10:35 AM

I created a fork with some extra msbuild tasks and targets to support getting, building and publishing packages.  We use teambuild for CI.

I import the targets by adding a line to the "common" targets file, so it is automatically available to all builds, then any build that has a packages.config file gets run.

http://nuget.codeplex.com/SourceControl/network/Forks/mr_miles/MSBuildTasks

Any dependent packages go into source control, and are then published to our internal feed, so we know the dependencies are always there and can't be pulled.  Works well so far, though I foresee a point where there are multiple builds depending on different versions of the same package that may cause problems.

I also started writing an agent that scans the dependencies feed and looks in the main repositories for newer versions, and notifies people that there are newer versions, but I haven't finished it yet.