I've since started publishing final releases, and now I realize that this isn't about dev versions vs. final versions. Any Python package that I publish using the Jenkins Artifactory plugin ends up at the root level of the repo. If I deploy using setup.py, the package lands in a nested directory. So now I'm trying to figure out if I can configure the Jenkins plugin to do the latter.
-- View this message in context: http://forums.jfrog.org/PyPI-repo-and-development-releases-tp7580973p7580974.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
