All of lore.kernel.org
 help / color / mirror / Atom feed
From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Anna Schumaker <anna@kernel.org>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH v2 2/3] codereadyrepo: Repo name for Oracle Linux
Date: Sat, 14 Dec 2024 12:01:38 -0500	[thread overview]
Message-ID: <20241214170139.253602-3-cel@kernel.org> (raw)
In-Reply-To: <20241214170139.253602-1-cel@kernel.org>

From: Chuck Lever <chuck.lever@oracle.com>

The name of the CodeReady Builder repo on Oracle Linux is different
than the other cases that the codereadyrepo role already supports.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 playbooks/roles/codereadyrepo/tasks/main.yml | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/playbooks/roles/codereadyrepo/tasks/main.yml b/playbooks/roles/codereadyrepo/tasks/main.yml
index 7cf6d83bcccf..b1d62eeb384c 100644
--- a/playbooks/roles/codereadyrepo/tasks/main.yml
+++ b/playbooks/roles/codereadyrepo/tasks/main.yml
@@ -6,6 +6,13 @@
     - ansible_distribution == 'RedHat'
     - not devconfig_custom_yum_repofile
 
+- name: Select the Oracle Linux CodeReady Builder repo
+  ansible.builtin.set_fact:
+    codeready_repo: "ol9_codeready_builder"
+  when:
+    - ansible_distribution == 'OracleLinux'
+    - not devconfig_custom_yum_repofile
+
 - name: Select the CentOS CodeReady Builder repo
   ansible.builtin.set_fact:
     codeready_repo: "crb"
-- 
2.47.1


  parent reply	other threads:[~2024-12-14 17:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14 17:01 [PATCH v2 0/3] Recent fixes cel
2024-12-14 17:01 ` [PATCH v2 1/3] codereadyrepo: Refactor to prepare for more complex usage scenarios cel
2024-12-14 17:01 ` cel [this message]
2024-12-14 17:01 ` [PATCH v2 3/3] codereadyrepo: Enable codeready-builder for AWS's RHEL 9 cel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241214170139.253602-3-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=anna@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=kdevops@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.