![]() This is done in the General Settings step of the Build ConfigurationĪnd with that, we’re done. We need instruct TeamCity to ouput the results of this folder as artifacts. In this step ( NuGet Pack Build Type), we can just configure the output for the package to point to some specific folder, for instance packages Since TeamCity itself is going to be a NuGet server, the step to publish a package is no longer required. If by chance the Public Url is not available, you will probably see a message telling you that you need to enable the Guest account in TeamCity, which can be done from the General tab. The same screen with then display two different feeds: a public and a private one: Go to Administration | Server Configuration | NuGet tabĬlick on the Enable button to enable it. ![]() Enabling TeamCity as NuGet and making packages available consists of two steps:ġ. All that is covered in detail in the previous post I wrote, so please read that first if you’re not familiar with the process. I am not going to cover how to pack and publish packages in this post. The best part of it is that it is so simple, that I had to take up the rest of this blog with the previous nonsense just to give it some meat. The same server that builds your projects, runs your tests, packs and publishes your packages can now also serve them. At the end of the day, its another service to manage.įortunately, you now have a third option: TeamCity. Setting up your own NuGet repository also requires managing permissions and whatnot separately. With the local share you now require sharing of folders and permissions. ![]() Copy nuget packages to a local share and have everyone read off of thatīoth of these options come with their own share of overhead. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |