Add existing nuget package to the feed

Hi

I've already read tons of articles and forum's threads but still it's not clear for my=)
I've got a simple task: establish my company's local nuget repository to ensure developers can add only approved libs/frameworks
I can setup such a repository in any shared folder but I want to leverage TeamCity's inbuilt capabilities
For example I'm doing the following with the existing nuget package NPOI.1.2.5.nupkg
* copy it to the {teamcity installation dir}\JetBrains\TeamCity\system\pluginData\jetbrains.nuget\nupkg
* I can see it propagaged to agent and tools folders
* I can see it propagated to all installed agents automatically
But I can't see it in the feed url http://[host]/httpAuth/app/nuget/v1/FeedService.svc/Packages() and Visual Studio returns empty list of available packages
Trying to obtain list of packages from TeamCity's feed using powershell commands also returns no results
What am I doing wrong?=)

I'm using TeamCity 7.1.2

6 comments
Comment actions Permalink

I can't believe there is no answer for this=)

0
Comment actions Permalink

Alex,

Nuget feed is served on TeamCity web server side. Build agents are used to run your builds, package artifacts, and upload them back on TeamCity server. But after a build is finished, build agent's work is finished, and it is not involved in the process anyhow.
The only supported way to install TeamCity plugins is to put them into <Data>\plugins folder. Other modifications may break your TeamCity installation, and will add problems with future upgrades.

You need to create a build configuration that will publish all required packages as its build artifacts. Then these packages will be added to the NuGet feed automatically.

0
Comment actions Permalink

mkuzmin wrote:


The only supported way to install TeamCity plugins is to put them into <Data>\plugins folder. Other modifications may break your TeamCity installation, and will add problems with future upgrades.

Mike

I'm sure why you wrote about plugins since I raised a question about existing nuget packages. But I guess it's clear that Team City at the moment doesn't offers full NuGet server capabilities which can be used to establish company's local repository

Thanks

0
Comment actions Permalink

Alex,

When you build your own packages, TeamCity can host them directly, so you don't have to setup and maintain standalone NuGet repository.
But your case is different, and here we're not going to compete with Microsoft's NuGet server.

0
Comment actions Permalink

OK a few years later, but thank you Michael. JetBrain's straight forward, honest/frank, response saves me time looking further.

0

Please sign in to leave a comment.