Story #4687: As a user, I can use either Python or Ruby bindings to interact with Pulp
configure Travis to publish pulpcore-client to PyPI
Another stage needs to be added to the travis config. This stage needs to run only when building a tag. It should run after pulpcore has been published to PyPI. This stage needs to use pulp-swagger-codegen to build the pulpcore-client package and upload it to PyPI.
Problem: user can't specify a version for generated bindings
Solution: allow user to specify the full version string
This patch updates generate.sh to accept an optional third parameter. This parameter represents the full version string that should be used when generating the client library.
Problem: publish of client fails if version has not changed
Solution: check rubygems.org and pypi.org before publishing
This patch does multiple things:
- Corrects the version string used when publishing Ruby Gem
- Reduces the frequency of publishing of pulp_file-client to PyPI
- Adds a check for existence of package about to be built. If it exists, the script exits before trying to build the client package again.
Problem: publish to rubygems.org and pypi.org can fail
Solution: check if the version of the client already exists
This patch adds an additional step to each of the pulpcore-client publish scripts. This step checks if the version of the client that is about to be built already exists. If the client version exists, the script exits without trying to build the package again.
Please register to edit this issue