Project

Profile

Help

Task #6796

Story #6793: [Epic] As a pulp_installer user, I can install Pulp from RPMs

Create CI for installing Pulp from RPMs

Added by mdepaulo@redhat.com over 1 year ago. Updated over 1 year ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
Sprint:
Quarter:

Description

This should include specifying the name of the repo to add as a variable.

Associated revisions

Revision 184f1235 View on GitHub
Added by Mike DePaulo over 1 year ago

As a pulp_installer user, I can install Pulp from RPMs

Heavily adapted from "allow installing pulp from packages"

https://github.com/pulp/pulp_installer/pull/188

Includes:

  1. Dropping the fixed repo from the old PR.
  2. Add var pulp_pkg_repo (currently only yum/dnf)
  3. Finish cleaning up pulp_webserver_static_dir
  4. Many new variables, but still using the overall pulp_install_plugins.
  5. Testing upgrades with new images on quay (can't truly test until RPM updates are issued)
  6. Cron/branch CI: Adding py38 testing
  7. PR CI: Move upgrade testing from py37 to py38, and testing from RPMs on py37.
  8. Deduplicating the tasks for checking plugins for nginx/apache snippets.
  9. Using pulp_django_admin_paths list var because RPMs often use different names for django-admin.
  10. Note: Rest of tasks should be package manager independent.
  11. pulp_upgraded_manually variable in case users ran yum update
  12. package only variables in seperate section of the pulp README.md.

fixes: #6793

Includes these subtasks implemented: re: #6794 re: #6795 re: #6796 (It was easiest to implement them all in one PR.)

Revision 184f1235 View on GitHub
Added by Mike DePaulo over 1 year ago

As a pulp_installer user, I can install Pulp from RPMs

Heavily adapted from "allow installing pulp from packages"

https://github.com/pulp/pulp_installer/pull/188

Includes:

  1. Dropping the fixed repo from the old PR.
  2. Add var pulp_pkg_repo (currently only yum/dnf)
  3. Finish cleaning up pulp_webserver_static_dir
  4. Many new variables, but still using the overall pulp_install_plugins.
  5. Testing upgrades with new images on quay (can't truly test until RPM updates are issued)
  6. Cron/branch CI: Adding py38 testing
  7. PR CI: Move upgrade testing from py37 to py38, and testing from RPMs on py37.
  8. Deduplicating the tasks for checking plugins for nginx/apache snippets.
  9. Using pulp_django_admin_paths list var because RPMs often use different names for django-admin.
  10. Note: Rest of tasks should be package manager independent.
  11. pulp_upgraded_manually variable in case users ran yum update
  12. package only variables in seperate section of the pulp README.md.

fixes: #6793

Includes these subtasks implemented: re: #6794 re: #6795 re: #6796 (It was easiest to implement them all in one PR.)

History

#1 Updated by mdepaulo@redhat.com over 1 year ago

  • Status changed from NEW to MODIFIED

#2 Updated by fao89 over 1 year ago

  • Sprint/Milestone set to 3.5.0

#3 Updated by fao89 over 1 year ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF