Different repositories or sub directories for staging/qa/release RPM / YUM

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

Different repositories or sub directories for staging/qa/release RPM / YUM

David Lee

Any suggestions on if I should use separate repositories or sub directory/key for keeping dev/staging/qa/production YUM Repositories ?

The tools and API's seem to work either way ... any pros or cons ?

Separate repos seem to make sense as its easier to deal with permission issues.

Any suggestions welcome.

 

 

 

----------------------------------------

David A. Lee

[hidden email]

http://www.xmlsh.org

 


------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

Re: Different repositories or sub directories for staging/qa/release RPM / YUM

HughG_TMVSE

Hi David,

 

we use mainly Ivy repositories but I think the same reasoning will apply.  We went for separate repos for several reasons.

 

·         The permissions reasons you raised.

·         It is easier to be clear about the deletion/retention policy/automation in each repo.

·         It’s easy to build virtual repos which include only some “stages” and not others.

·         Artifactory’s UI and REST API for copying/moving (i.e., promoting) only copies between (the same path in) different repos, not from one path to another within a repo – at least, not in the 3.3.0 version we’re using.

 

Hope that helps,

 

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK
Tel + 44 (0)131 472 4792 / Fax + 44 (0) 131 472 4799
http://www.tmvse.com / [hidden email]

 

DISCLAIMER
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message.

 

From: David Lee [mailto:[hidden email]]
Sent: 24 August 2015 18:07
To: [hidden email]
Subject: [Artifactory-users] Different repositories or sub directories for staging/qa/release RPM / YUM

 

Any suggestions on if I should use separate repositories or sub directory/key for keeping dev/staging/qa/production YUM Repositories ?

The tools and API's seem to work either way ... any pros or cons ?

Separate repos seem to make sense as its easier to deal with permission issues.

Any suggestions welcome.

 

 

 

----------------------------------------

David A. Lee

[hidden email]

http://www.xmlsh.org

 


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

------------------------------------------------------------------------------

_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users