Project

Profile

Help

Task #4695

Story #4687: As a user, I can use either Python or Ruby bindings to interact with Pulp

configure Travis to publish pulpcore-client to rubygems.org

Added by dkliban@redhat.com about 2 years ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
API Bindings
Sprint:
Sprint 52
Quarter:

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 Ruby Gem and upload it to rubygems.org.

We will need to create a rubygems.org account and configure travis with credentials for publishing to there.

[0] https://github.com/pulp/pulp-swagger-codegen


Related issues

Copied from Pulp - Task #4694: configure Travis to publish pulpcore-client to PyPI CLOSED - CURRENTRELEASE

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision 57d9b5b3 View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: can't generate nightly versions

Solution: add ability to pass in a string to append to version

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

Revision 2a8c1e28 View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: pulpcore-client ruby gem not being published

Solution: start publishing pulpcore-client ruby gem nightly

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

Revision 33d7aa8c View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: pulpcore-client ruby gem published too often

Solution: only publish when cron is building the project

closes: #4695 https://pulp.plan.io/issues/4695

Revision c366a900 View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: pulp_file_client not published as ruby gem

Solution: publish pulp_file_client ruby gem when building project

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

Revision 1c72a150 View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: pulp not provisioned during gem publish step

Solution: install pulp in the install install script

This patch updates how Pulp is installed by Travis. It is now installed using ansible-pulp. The install step now happens as part of the install script.

This also adds MariaDB testing.

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

Revision 6d93e53b View on GitHub
Added by dkliban@redhat.com about 2 years ago

Problem: wrong user owns pulp_file_client

Solution: change ownership to travis user

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

Revision 82acc942 View on GitHub
Added by dkliban@redhat.com about 2 years ago

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

Revision 61aac764 View on GitHub
Added by dkliban@redhat.com about 2 years ago

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 about 2 years ago

  • Copied from Task #4694: configure Travis to publish pulpcore-client to PyPI added

#2 Updated by bmbouter about 2 years ago

  • Tags Pulp 2 added

#3 Updated by bmbouter about 2 years ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#4 Updated by dkliban@redhat.com about 2 years ago

  • Tags deleted (Pulp 2)

#5 Updated by dkliban@redhat.com about 2 years ago

  • Tags API Bindings added

#6 Updated by ipanova@redhat.com about 2 years ago

  • Sprint set to Sprint 52

#7 Updated by dkliban@redhat.com about 2 years ago

  • Project changed from RPM Support to File Support
  • Subject changed from configure Travis to publish pulpcore-client to rubygems.org to configure Travis to publish pulp_file-client to rubygems.org

#8 Updated by dkliban@redhat.com about 2 years ago

  • Project changed from File Support to Pulp
  • Subject changed from configure Travis to publish pulp_file-client to rubygems.org to configure Travis to publish pulpcore-client to rubygems.org
  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com

#9 Updated by dkliban@redhat.com about 2 years ago

  • Status changed from ASSIGNED to MODIFIED
  • % Done changed from 0 to 100

#10 Updated by dkliban@redhat.com about 2 years ago

  • Status changed from MODIFIED to POST

#11 Updated by dkliban@redhat.com about 2 years ago

  • Status changed from POST to MODIFIED

#12 Updated by bmbouter over 1 year ago

  • Sprint/Milestone set to 3.0.0

#13 Updated by bmbouter over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF