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

Drop Pulpcore 3.16, 3.17 & 3.18 pipelines #383

Merged
merged 1 commit into from
Nov 28, 2023

Conversation

ekohl
Copy link
Member

@ekohl ekohl commented Nov 26, 2023

These belong to EOL Katello versions. Recently we've been seeing problems provisioning nodes in CentOS CI so this reduces the number of nodes we consume.

Copy link
Member

@evgeni evgeni left a comment

Choose a reason for hiding this comment

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

I think you can also drop 3.21

@ekohl
Copy link
Member Author

ekohl commented Nov 26, 2023

I wondered if there was a downstream concern, since it's used in Foreman 3.5

@evgeni
Copy link
Member

evgeni commented Nov 26, 2023

I'll leave the definitive answer to @Odilhao but I don't think the upstream pipes matter for that case

@Odilhao
Copy link
Member

Odilhao commented Nov 26, 2023

Let's nuke it and keep 3.22, 3.28 and 3.39, too many python 3.9 to cherrypick and release atm.

These belong to EOL Katello versions. Recently we've been seeing
problems provisioning nodes in CentOS CI so this reduces the number of
nodes we consume.
@ekohl ekohl force-pushed the drop-old-pulpcore-pipelines branch from a48c75d to 99b4735 Compare November 28, 2023 09:17
@evgeni evgeni merged commit 746bf7c into theforeman:master Nov 28, 2023
2 checks passed
@ekohl ekohl deleted the drop-old-pulpcore-pipelines branch November 28, 2023 10:40
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.

3 participants