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

Add config for Katello 4.14 #577

Merged
merged 1 commit into from
Aug 26, 2024
Merged

Conversation

chris1984
Copy link
Member

@pcreech here is the 4.14 config

@ekohl
Copy link
Member

ekohl commented Aug 20, 2024

@chris1984 release engineering doesn't use tool_belt at all anymore (since Foreman 3.10). AFAIK these days it's only for the release owner to do cherry picks.

@chris1984
Copy link
Member Author

@chris1984 release engineering doesn't use tool_belt at all anymore (since Foreman 3.10). AFAIK these days it's only for the release owner to do cherry picks.

@ekohl I was just tagging him since he was the release engineer to get it merged. You are right it's only used for cherry-picks now. I was getting a PR based on the branching docs:

Add tool_belt config for new release:
Create a new yaml file using the nightly Katello config as a template: [tool_belt configs](https://github.com/theforeman/tool_belt/tree/master/configs/katello)
Manually update the following sections:
releases: update to current release. Move the previous ‘current’ release to prior_releases below.
prior_releases: Remove the oldest prior_release (check with that release owner first to see if there’s a reason it should stay)
repos: Update branch names to current versions, including any new releases that need to happen
ignores: Delete all items from this list and start fresh (this will be used for cherry-picks later)
tags: update Katello version number in all values. Check the nightly config to see if any tags/repos need to be updated

chris1984

This comment was marked as duplicate.

@evgeni evgeni merged commit 49eefdc into theforeman:master Aug 26, 2024
1 check passed
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