Distributing files via Bintray includes three steps: creating a version, uploading the files and publishing the files.
-
Creating a version: Uploaded files are associated with a specific version of a package. Some upload methods can create the version automatically as part of the upload; with other methods you will need to create a target version from the Bintray UI or using REST.
-
Uploading: Upload your files using one of the methods described in the "Uploading" section. After uploading your files, the files have a status of "un-published". This means that in the Bintray UI they are only visible to you and can only be downloaded with your username and API Key. You may discard all or some of your uploaded files when they are "un-published", before anyone sees or downloads them.
-
Publishing: Once you are good to go, you can publish your files and make them visible and available to all Bintray users. Publishing can be done via REST (as part of the upload or separately) or using the UI (an unpublished content notice appears on your screen, with links to publish or discard the files). Some upload methods also allow you to publish your files automatically upon uploading, letting you skip the publishing step.
- Use the cURL command to upload your files:
curl -T <FILE.EXT> -uaursu:<API_KEY> https://api.bintray.com/content/aursu/custom/<YOUR_COOL_PACKAGE_NAME>/<VERSION_NAME>/<FILE_TARGET_PATH>
- The repository-wide RPM metadata will be auto-calculated by Bintray.
Python script (compatible with Python 2.6 ad Python 2.7) for uploading RPM packages to Bintray
https://github.com/aursu/docker-rpmbuild/blob/master/createrepo/scripts/bintray.py