From: pscheir <ps...@gm...> - 2013-08-30 11:31:49
|
Hi, is there a way to enforce the layout of a repository during deploy time? I have the standard repository libs-release-local with maven2 layout. >From the following three deployments I would like to have deployment 2 and 3 not accepted as the layout is not followed: 1. curl --user admin:password --upload-file abc.zip http://localhost:8081/artifactory/simple/libs-release-local/xxx/yyy/2.0/yyy-2.0.zip 2. curl --user admin:password --upload-file abc.zip http://localhost:8081/artifactory/simple/libs-release-local/yyy/2.1/yyy-2.1.zip 3. curl --user admin:password --upload-file abc.zip http://localhost:8081/artifactory/simple/libs-release-local/xxx /cobra/2.2/yyy.zip Interestingly I have this behavior in “Test Artifact Path Resolution” under “Edit Repository Layout”. Thanks, Peter -- View this message in context: http://forums.jfrog.org/Enforce-repository-layout-tp7579041.html Sent from the Artifactory - Users mailing list archive at Nabble.com. |
From: sharonalin <sh...@jf...> - 2013-09-01 13:19:43
|
Hi Peter, Currently we only enforce Maven2 layout checks for pom files. We validate that the groupId/artifactId specified in the .pom file match the deployment path. You can perform such check by developing a user plugin which will perform the validation before the deployment. You can find more information about the user plugin in Artifactory wiki: http://www.jfrog.com/confluence/display/RTF/User+Plugins User plugin is a feature available in our Pro version. Regards, Sharon -- View this message in context: http://forums.jfrog.org/Enforce-repository-layout-tp7579041p7579050.html Sent from the Artifactory - Users mailing list archive at Nabble.com. |
From: pscheir <ps...@gm...> - 2013-09-10 12:58:45
|
Thanks Sharon for pointing that out, I will look into this when the time has come... Best, Peter -- View this message in context: http://forums.jfrog.org/Enforce-repository-layout-tp7579041p7579090.html Sent from the Artifactory - Users mailing list archive at Nabble.com. |