Provide dedicated upload tasks for the various package types.

[nbaju1]

Manually constructing the target path for a package is hard to generalize using the generic upload task.

Using Python as an example: When uploading a package with twine the package will automatically be uploaded in the correct folder path, i.e. "pypi-local/package-name/1.0.1/package_name-1.0.1.tar.gz" when you target the file "package_name-1.0.1.tar.gz". Similar for the corresponding .whl file type. With the generic JFrog upload task I have to manually specify the target path for each package. There might be a way to construct the pattern and target parameters in the file spec such that this can be generalized, but I have not been successful in doing so. It also leaves room for error if people are adhering to the correct folder structure when uploading their packages.

Would be nice to have a designated upload task for Python (and the other package types) in which you only need to specify the target repository and the local package file.

[sverdlov93]

Hi @nbaju1, Currently, we have no specific task for twine or other Python package managers except pip/pipenv/poetry. The way to go here is to use twine command to build the tar.gz/whl files and upload them to Artifactory. You can see the following pip example - https://github.com/jfrog/project-examples/tree/master/python-example/pip-example.