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

[richm]

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 definitions in the parallel test playbook plan to use the current development site name instead of the deprecated one.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Testing Farm CI playbook plan configuration so yum repositories on older machines point to the new devel site instead of the legacy site, ensuring tests run against the correct repo endpoints.

File-Level Changes

Change	Details	Files
Redirect yum repositories in Testing Farm-related CI configuration from the old site hostname to the new devel site hostname.	Replace occurrences of the legacy yum base URL/hostname with the new devel site hostname in the test playbook plan configuration Ensure all relevant Testing Farm machine/repo definitions now reference the updated site name so older machines no longer use the deprecated endpoint	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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider centralizing the site name (e.g., as a variable or shared include) instead of hardcoding it in the playbook plan so future site renames only require changing it in one place.
• Double-check whether there are any other CI plans or machine setup scripts that still reference the old site name and update them in the same way for consistency.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider centralizing the site name (e.g., as a variable or shared include) instead of hardcoding it in the playbook plan so future site renames only require changing it in one place.
- Double-check whether there are any other CI plans or machine setup scripts that still reference the old site name and update them in the same way for consistency.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}