Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide RHEL 9 based jenkins slave image #1766

Open
liangxia opened this issue Feb 28, 2024 · 17 comments
Open

Provide RHEL 9 based jenkins slave image #1766

liangxia opened this issue Feb 28, 2024 · 17 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@liangxia
Copy link
Member

Hi, would it be possible to provide a RHEL 9 based Jenkins slave image ? Thank you.

@divyansh42
Copy link
Contributor

Hi @liangxia
We are working on it. Will keep you posted once we have it.

@arrfab
Copy link

arrfab commented Apr 2, 2024

We (CentOS) are currently also interested into that : we have an openshift cluster deployed , with Jenkins from official catalog, but our workload is using a modified container to satisfy dependencies for our tests.

As it's for public CI , we just reused the original origin-jenkins-agent-base:latest container, which is based from UBI8, and just add needed .repo from CentOS Stream 8
As Stream 8 is going EOL end of May (so approaching soon) we'd like to rebase to newer/refreshed upstream origin-jenkins-agen-base image, itself built from UBI9, so that we can just "convert" it to Stream 9 and still have our existing CI tenants (including other Red Hat upstream projects) be able to transparently have up2date container for the ansible orchestration tasks.

Do we have a kind of ETA for the rebased agent image ? We'd be more than happy to give it a try somewhere and report feedback here

@gpei
Copy link

gpei commented Jun 13, 2024

@divyansh42 Hi, do we have any update on this?

@divyansh42
Copy link
Contributor

@gpei Due to changing priorities, I am not working on this anymore.
@sayan-biswas @ramessesii2 should be the right person to provide further updates on this.

@ramessesii2
Copy link

Hey @gpei, there's WIP #1769 related to this. Though we're yet to prioritize it for completion.
cc @avinal

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 16, 2024
@arrfab
Copy link

arrfab commented Sep 16, 2024

wondering if that's still somehow in scope somehow.
We'd appreciate any kind of ETA or even answer about "no, we'll never implement it or even stop completely jenkins containers" so that users can eventually plan something about it.
TIA :)

@avinal
Copy link
Member

avinal commented Sep 16, 2024

Hey @arrfab, yes, this story is still on our backlog. I cannot give any ETA on it yet.

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 17, 2024
@avinal
Copy link
Member

avinal commented Oct 17, 2024

This is in progress. With 4.16 and 4.17 release, there would be rhel-9 based images available.

@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci bot closed this as completed Nov 16, 2024
Copy link
Contributor

openshift-ci bot commented Nov 16, 2024

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@axieum
Copy link

axieum commented Nov 16, 2024

/reopen

Copy link
Contributor

openshift-ci bot commented Nov 16, 2024

@axieum: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@avinal
Copy link
Member

avinal commented Nov 18, 2024

/reopen

@avinal
Copy link
Member

avinal commented Nov 18, 2024

/remove-lifecycle rotten
/lifecycle frozen

@openshift-ci openshift-ci bot reopened this Nov 18, 2024
@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Nov 18, 2024
Copy link
Contributor

openshift-ci bot commented Nov 18, 2024

@avinal: Reopened this issue.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

8 participants