Skip to content

ci: fix yum repos to use devel site instead of old site name [citest_skip]#301

Merged
richm merged 1 commit intomainfrom
use-devel-site-yum-repo
Apr 1, 2026
Merged

ci: fix yum repos to use devel site instead of old site name [citest_skip]#301
richm merged 1 commit intomainfrom
use-devel-site-yum-repo

Conversation

@richm
Copy link
Copy Markdown
Collaborator

@richm richm commented Apr 1, 2026

Some of the older Testing Farm machines refer to the old site name in the yum repos.
Ensure that they use the correct site name.

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

CI:

  • Switch Testing Farm yum repository references from the old site name to the current devel site.

…skip]

Some of the older Testing Farm machines refer to the old site name in the yum repos.
Ensure that they use the correct site name.

Signed-off-by: Rich Megginson <rmeggins@redhat.com>
@richm richm self-assigned this Apr 1, 2026
@sourcery-ai
Copy link
Copy Markdown

sourcery-ai bot commented Apr 1, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Testing Farm CI yum repository configurations to use the current devel site name instead of the deprecated site name in the parallel playbook plan.

File-Level Changes

Change Details Files
Update CI Testing Farm yum repo configuration references from the old site hostname to the current devel site hostname.
  • Adjusted yum repository base URLs or mirrorlist URLs to replace the legacy site name with the new devel site name for Testing Farm machines.
  • Ensured parallel playbook plan now consistently uses the updated site name so older Testing Farm machines no longer reference the deprecated host.
plans/test_playbooks_parallel.fmf

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • If the new yum repo hostnames are hard-coded in the plan, consider centralizing them in a single variable or macro so future domain changes can be applied in one place instead of touching multiple plans.
  • Ensure the logic that switches to the new site name is scoped only to the affected Testing Farm environments so that systems already using the correct configuration are not inadvertently altered.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- If the new yum repo hostnames are hard-coded in the plan, consider centralizing them in a single variable or macro so future domain changes can be applied in one place instead of touching multiple plans.
- Ensure the logic that switches to the new site name is scoped only to the affected Testing Farm environments so that systems already using the correct configuration are not inadvertently altered.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@richm richm merged commit 3da9750 into main Apr 1, 2026
14 checks passed
@richm richm deleted the use-devel-site-yum-repo branch April 1, 2026 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant