Just FYI, the NuGet team has been discouraging automating the posting of *every* build to the primary NuGet feed and recommends that ppl only post (automated or otherwise) so-called 'released versions' to the main feed.
This is for a few reasons, IIRC... 1) NuGet lacks any (enforced) way to distinguish 'released, please use this' packages from 'trunk daily build, etc, use at your own risk' packages 2) The default NuGet behavior for packages, dependencies, etc is "this version or later" and so constant churn in the latest version avail. isn't really desired in NuGet as it will potentially cause trouble for pkgs that depend on you or pkg or adopters of your pkg that accept 'always get me the latest pkg' I know all of this is contrary to what many of us consider to be the point of a CI build (e.g. If it builds + passes the tests it should be considered potentially releasable, so why NOT automate its release?) but until NuGet does something to make it easy to distinguish betw 'official release' pkg and 'CI build from check-in' pkg automating every build deployed to NuGet is being discouraged by the NuGet team. Ideas to mitigate this include introducing 'pkg categories' in NuGet or having a sep. official NuGet feed for dailies/check-in pkgs that aren't official releases. But until NuGet matures to address this, they are discouraging Continuous Delivery-style posting of pkgs direct from every CI build AFAIK based on my conversations with them. That said, AFAIK there's no *technical* reason you couldn't do what you're suggesting :) HTH, -Steve B. -----Original Message----- From: miles <[email protected]> Sender: [email protected] Date: Fri, 1 Apr 2011 05:32:04 To: Rhino Tools Dev<[email protected]> Reply-To: [email protected] Subject: [rhino-tools-dev] Rhino.ETL nuget package Hi, I've created a nuget package of the current rhino.etl trunk. It's pretty cool as it pulls in all the relevant boo, rhino.dsl, filehelpers and log4net dependencies that are needed automatically, from the other packages published there. I noticed that changes cause successful new builds to end up here: http://builds.hibernatingrhinos.com/builds/Rhino-ETL Is there any mileage in getting the packages automatically fed to the nuget feed at the same time? It doesn't look too hard, though I didn't manage to get the powershell-based build to work at all. Cheers, Miles -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en. -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
