Pulp

Problem: pulpcore-client not published to PyPI

Solution: add another stage that publishes pulpcore-client to PyPI

This patch adds another stage to the deploy pipeline. During this stage, the pulpcore-client package is generated and pushed to PyPI.

re: #4694 https://pulp.plan.io/issues/4694

Problem: python client version string is malformed

Solution: use + instead of - in the Python version string

re: #4694 https://pulp.plan.io/issues/4694

Problem: python version string needs a number after the +

Solution: try using 1 as the number for now

re: #4694 https://pulp.plan.io/issues/4694

Problem: can't have + in Python version string

Solution: use .dev.1 for now

In the future this string will contain the number of commits since the tag

re: #4694 https://pulp.plan.io/issues/4694

Problem: the prerelease version always ends in .dev.1

Solution: change the 1 to a parameter passed in by user

re: #4694 https://pulp.plan.io/issues/4694

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.

re: #4694 https://pulp.plan.io/issues/4694

Problem: python client publishes bad version string

Solution: use commit count instead of hash

This patch also makes the same change for the Ruby Gem being published.

re: #4694 https://pulp.plan.io/issues/4694

Problem: pulpcore-client is published too frequently

Solution: configure Travis to only publish on CRON builds

re: #4694 https://pulp.plan.io/issues/4694

Problem: pulp_file-client not being published to PyPI

Solution: configure Travis to publish pulp_file-client to PyPI

This also limits how frequently the pulp_file_client Ruby Gem is published.

re: #4694 https://pulp.plan.io/issues/4694

Problem: publish of client fails if version has not changed

Solution: check rubygems.org and pypi.org before publishing

This patch does multiple things:

1. Corrects the version string used when publishing Ruby Gem
2. Reduces the frequency of publishing of pulp_file-client to PyPI
3. 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.

re: #4694 https://pulp.plan.io/issues/4694 re: #4695 https://pulp.plan.io/issues/4695

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.

re: #4694 https://pulp.plan.io/issues/4694 re: #4695 https://pulp.plan.io/issues/4695