Project

Profile

Help

Task #76

closed

Automatically run repoclosure for all arches/dists after building pulp repos

Added by Anonymous over 9 years ago. Updated almost 3 years ago.

Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

This task is related to build stuff, not Pulp itself:)

RPM dependences are occasionally missed during a build, especially for platforms we do not commonly use like el5. This occurs about once every two or three weeks for Pulp repos; QE will find that an RPM is missing while doing an install.

One way to find such issues quickly is to run repoclosure on each repos before publishing. This is typically done as one command per repo; an example is at https://fedoraproject.org/wiki/QA:Testcase_Mediakit_Repoclosure.

This step is typically done during the build/release process before QE handoff, but could also be done by QE. Ideally this could be run as part of the new build process.

This should be done in the nightly Jenkins build repos job. This should be done using Docker if possible because it needs to be run on each arch and dist.

Actions #1

Updated by rbarlow over 9 years ago

  • Tracker changed from Story to Task
Actions #2

Updated by rbarlow over 9 years ago

  • Project changed from 22 to Pulp
Actions #3

Updated by bmbouter over 9 years ago

  • Subject changed from [task] automatically run repoclosure for all arches/dists as part of integration tests to Automatically run repoclosure for all arches/dists as part of integration tests
Actions #4

Updated by cduryee about 9 years ago

  • Tags Sprint Candidate added

This would find issues before QE finds them. One these issues comes up maybe every 2 weeks.

Actions #5

Updated by mhrivnak about 9 years ago

Can someone speak to how much effort this would take?

And to clarify, does this mean we would run repoclosure on the pulp repository itself after doing a build of pulp's own RPMs?

And when you say "integration tests", do you mean the test suite QE maintains? If yes, why are we the ones adding it? If no, then what are you talking about?

Generally, this proposal needs a lot more detail. A blank description is almost never sufficient.

Actions #6

Updated by cduryee about 9 years ago

  • Description updated (diff)
Actions #7

Updated by cduryee about 9 years ago

  • Subject changed from Automatically run repoclosure for all arches/dists as part of integration tests to Automatically run repoclosure for all arches/dists after building pulp repos
  • Description updated (diff)
Actions #8

Updated by mhrivnak about 9 years ago

  • Priority changed from Normal to Low
Actions #9

Updated by bmbouter about 9 years ago

  • Description updated (diff)
  • Tags Groomed added
Actions #10

Updated by bmbouter almost 9 years ago

  • Groomed set to Yes
  • Tags deleted (Groomed)
Actions #11

Updated by bmbouter almost 9 years ago

  • Sprint Candidate set to Yes
  • Tags deleted (Sprint Candidate)
Actions #12

Updated by mhrivnak almost 8 years ago

  • Sprint Candidate changed from Yes to No
Actions #13

Updated by bmbouter about 5 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #14

Updated by bmbouter about 5 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions #15

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF