Task #4694
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
0%
Description
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[0] to build the pulpcore-client package and upload it to PyPI.
Related issues
Associated revisions
Revision d95745ad
View on GitHub
Problem: python client version string is malformed
Solution: use + instead of - in the Python version string
Revision 6c6ffc36
View on GitHub
Problem: python version string needs a number after the +
Solution: try using 1 as the number for now
Revision 3f36ec34
View on GitHub
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
Revision 613f57e5
View on GitHub
Problem: the prerelease version always ends in .dev.1
Solution: change the 1 to a parameter passed in by user
Revision 36a48eed
View on GitHub
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.
Revision f0f01f03
View on GitHub
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.
Revision 93939d86
View on GitHub
Problem: pulpcore-client is published too frequently
Solution: configure Travis to only publish on CRON builds
Revision 33fcaadb
View on GitHub
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.
Revision 82acc942
View on GitHub
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.
re: #4694 https://pulp.plan.io/issues/4694 re: #4695 https://pulp.plan.io/issues/4695
Revision 61aac764
View on GitHub
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
History
#1
Updated by dkliban@redhat.com almost 2 years ago
- Copied to Task #4695: configure Travis to publish pulpcore-client to rubygems.org added
#2
Updated by bmbouter almost 2 years ago
- Tags Pulp 2 added
#3
Updated by bmbouter almost 2 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
#4
Updated by dkliban@redhat.com almost 2 years ago
- Tags deleted (
Pulp 2)
#5
Updated by dkliban@redhat.com almost 2 years ago
- Tags API Bindings added
#6
Updated by ipanova@redhat.com almost 2 years ago
- Sprint set to Sprint 52
#7
Updated by dkliban@redhat.com almost 2 years ago
- Project changed from RPM Support to Pulp
#8
Updated by dkliban@redhat.com over 1 year ago
- Status changed from NEW to POST
- Assignee set to dkliban@redhat.com
#9
Updated by dkliban@redhat.com over 1 year ago
- Status changed from POST to MODIFIED
#10
Updated by bmbouter about 1 year ago
- Sprint/Milestone set to 3.0.0
#11
Updated by bmbouter about 1 year ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Please register to edit this issue
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