My organization has been using Artifactory Pro to host PyPI repos for a
while, and now I'm setting up a separate development repo that will be
integrated into our Jenkins-based build pipeline. The development packages
are numbered using the PEP-440 development release scheme:
major.minor.micro.dev#, where the dev release number is the Jenkins build
number.
This seems to be working reasonably well, but I've noticed that within the
repository the dev releases don't get placed in version directories that are
under the main package directory. Instead, all of their files get placed at
the top level of the repository. This doesn't seem to prevent pip from
finding the right package to install, but in the long run it will probably
become more difficult to browse the repo when everything's sitting in one
place. The PyPI metadata does show the correct full version number for each
package.
I've tried a couple of different repo layouts to see if that would make a
difference, but it doesn't seem to. Would a custom layout work here?
Example of repo layout with one dev release and one final release of the
package:
<http://forums.jfrog.org/file/n7580973/Screen_Shot_2016-04-27_at_4.png>
--
View this message in context:
http://forums.jfrog.org/PyPI-repo-and-development-releases-tp7580973.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Artifactory-users mailing list
Artifactory-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/artifactory-users
