Re: How does Artifactory use repo layout patterns?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: How does Artifactory use repo layout patterns?

HughG_TMVSE

Hi again, all,

 

belatedly replying to my own message, after realizing that the response I got on this from JFrog was in personal email, not on-list.

 

The repository layouts are only used for the things described in <a href="http://www.jfrog.com/confluence/display/RTF2X/Repository&#43;Layouts#RepositoryLayouts-TheFreedomofCustomLayouts"> http://www.jfrog.com/confluence/display/RTF2X/Repository+Layouts#RepositoryLayouts-TheFreedomofCustomLayouts. It wasn't clear to me that that's an exhaustive list of what the patterns are used for but, in fact, it is.

 

Hope that helps someone else in future :-)

 

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: Greene, Hugh
Sent: 23 May 2013 13:59
To: '[hidden email]'
Subject: How does Artifactory use repo layout patterns?

 

Hi all,

 

I've relatively recently become one of the admins for our Artifactory (Open Source) 2.3.4 server, and am trying to understand how exactly Artifactory uses Repository Layout patterns.  We've started using Artifactory and Gradle relatively recently, with some custom Gradle plugins for C++ development.  Most of our repos are set up with the ivy-default pattern, which is as follows.

 

                [org]/[module]/[baseRev](-[folderItegRev])/[type]s/[module](-[classifier])-[baseRev](-[fileItegRev]).[ext]

 

However, we have a load of artifacts which are missing the "/[type]s" part, so don't actually match that pattern at all.

 

It seems, therefore, that Artifactory isn't using it to filter attempts to upload artifacts.  So, what is it using the pattern for?  I think it may be either or both of …

 

- Automatic clean-up of integration versions (if configured).

 

- On-the-fly mapping between repo formats (e.g., Maven and Ivy), because Artifactory can try to present one repo as if it were of another format.

 

I think it's NOT used (at least, by Gradle) to resolve Ivy's "latest.integration" or similar dynamic versions. For that, I think Gradle does a directory listing, looks through the ivy.xml files for ones with status="integration" (or milestone/release, since they're "greater"), and returns the "last" one (in lexicographic order by filename?).

 

Is it used for anything else?  I couldn't see any explanations in the online manual page about repo layout patterns, and I only inferred the above points from indirect comments on other pages.  Is it likely to cause us problems in future if artifacts don't match the pattern?

 

Thanks for any explanations anyone can give, especially ones which point to official online docs :-)

 

Regards,

 

Hugh Greene, Senior Software Developer
Toshiba Medical Visualization Systems Europe, Ltd
Bonnington Bond, 2 Anderson Place, Edinburgh EH6 5NP, UK

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.

 


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

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users