Best practice on repository layout for NuGet

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Best practice on repository layout for NuGet

HJScherer
This post was updated on .
hi, folks

we are wondering to license ArtiFactory Pro to manage artifacts rom our build process using Jenknis/Ant, NuGet, Git/GitFlow with several modules (products, libaries, components) with runtime and build dependencies.

Can we read somewhere about best practices how to setup a repository structure (several repositores for staging, production), how to map the builds from GitFlow branches (master, release, development) and therefore how to layout the repository folder structure.

We wil push Nuget packages, in addition C# (.NET) and C++  (native) artifacts and Setups (created by WiX) as well.

Would be nice to learn from some whitepapers as the ArtiFactory documentation we found is very functional focused.

best reagrds,
Heinz
Reply | Threaded
Open this post in threaded view
|

Re: Best practice on repository layout for NuGet

pscheir
Hi Heinz,

we have a similar infrastructure and I have wondered about this too:
http://forums.jfrog.org/Best-repository-layout-for-c-tc7579089.html

We now use a custom repository layout that is based on the way we have organized our binaries on the file server before. The layout can be seen here:
http://forums.jfrog.org/Max-Unique-Snapshots-tc7579352.html#a7579389
What can also see there is that Artifactory has some trouble with this custom layout.

We are currently testing a workflow with 3 repositories: One repository for snapshots, one for quality assurance (QA) and one for releases. Snapshots are generated by CI builds, if integration tests are successful the artifact is promoted to the QA repository. This repository is used by our testers, if tests are successful the build is promoted to the release repository. The advantage of this approach is that those teams that do not use CI can still manually release into the release repository.

Our artifacts are currently packaged as ZIP files (not Nuget). We tested Nuget and it worked fine. However our build infrastructure does not deliver Nuget yet.

Best regards, Peter

P.S. I am going to write you a personal e-mail, maybe we can have a phone call to exchange some ideas. I am located in Austria.
Reply | Threaded
Open this post in threaded view
|

Re: Best practice on repository layout for NuGet

Ariel

Hi Heinz


I will address both of your posts here.

Regarding to the setup a repository structure, Artifactory provide a 3 types of repositories: Local, Remote and Virtual.

Virtual repository can aggregate multiple repositories in it (local, remote, and virtual), and the resolution process should be against the virtual repositories.

You can create your own virtual repositories or use the defaults.

You can find more information about layouts here.


If you mentioned the Jenkins Artifactory plugin, I would recommend you to read more about the Generic (Freestyle) Builds that will probably fit better to your needs. The generic build, as for the rest of the builds using this plugin, allows you to resolve your code from Git, your artifacts from Artifactory and publish the build to Artifactory.

The Jenkins Artifactory plugin also supports Ivy-Ant Builds.


Artifactory supports NuGet repositories, Nuget layouts and allow you to push and resolve  Nuget packages to and from Artifactory using, curl, VisualStudio,  Nuget command line etc..


As for the staging and production repositories, Artifactory allows you a to use REST API commands including Build Promotion that can assist with releasing artifacts from staging to production repositories.


Basically Artifactory can store all file formats regardless to their extension (.dll, .H, lib)


As peter mentioned, you can configure a custom repository layout that is based on the way you want to organize your binaries on the file server.


BTW there is a great video, from the last Jenkins conference, regarding Jenkins + Nuget + Artifactory that you might find interesting :

http://www.youtube.com/watch?v=C5-98Fln1jg


Hope this helps,

Ariel




On Fri, Dec 27, 2013 at 7:34 AM, pscheir <[hidden email]> wrote:
Hi Heinz,

we have a similar infrastructure and I have wondered about this too:
http://forums.jfrog.org/Best-repository-layout-for-c-tc7579089.html

We now use a custom repository layout that is based on the way we have
organized our binaries on the file server before. The layout can be seen
here:
http://forums.jfrog.org/Max-Unique-Snapshots-tc7579352.html#a7579389
What can also see there is that Artifactory has some trouble with this
custom layout.

We are currently testing a workflow with 3 repositories: One repository for
snapshots, one for quality assurance (QA) and one for releases. Snapshots
are generated by CI builds, if integration tests are successful the artifact
is promoted to the QA repository. This repository is used by our testers, if
tests are successful the build is promoted to the release repository. The
advantage of this approach is that those teams that do not use CI can still
manually release into the release repository.

Our artifacts are currently packaged as ZIP files (not Nuget). We tested
Nuget and it worked fine. However our build infrastructure does not deliver
Nuget yet.

Best regards, Peter

P.S. I am going to write you a personal e-mail, maybe we can have a phone
call to exchange some ideas. I am located in Austria.



--
View this message in context: http://forums.jfrog.org/Best-practice-on-repository-layout-for-NuGet-tp7579514p7579516.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users