Q1:
I have a PyPi enabled repo (my-pypi-repo) where I can publish my packages.
When uploading via ,I get a structure like this:The problem is this
structure will not match any "allowed" repo layout in Artifactory, since or
are mandatory:Pattern '[module]/[baseRev]/[module]-[baseRev].[ext]' must
at-least contain the tokens 'module', 'baseRev' and 'org' or 'orgPath'.I
managed to publish to a path by 'hacking' the package name to
'myorg/my_package', but then cannot find it, so it's pretty useless
Q2:
Has anyone tried the "ci-repo" and "releases-repo" with promotion for
Python?What I would like to achieve:*CI repo:*
my_package-1.2.3+build90.tar.gz (I don't care that much about the [org]When
this artifact gets promoted (build metadata gets dropped):*Releases repo:*
my_package-1.2.3.tar.gzI can achieve this via repo layouts (providing I
resolve Q1). The problem is how to deal with the "embedded" version inside
my Python script. I'd rather not rebuild the package again, for best
practices.
--
View this message in context:
http://forums.jfrog.org/PyPi-repo-layout-and-ci-releases-repos-with-promotion-tp7580245.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
