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

ENT-11338: Adjusted cfbs packaging on rhel-8 to use platform-python (3.21) #1399

Merged
merged 1 commit into from
Feb 20, 2024

Conversation

craigcomstock
Copy link
Contributor

This is done via an rpm macro.
Build host policy is updated to included needed packages to achieve this. Only on rhel-8.
rhel-9 apparently removed this platform-python as dnf requires python39.

Ticket: ENT-11338
Changelog: title
(cherry picked from commit c307618)

Conflicts:
ci/cfengine-build-host-setup.cf

I added all of the build host related files in this commit to 3.21.x as we can track different build host setups eventually to be used in our pipelines instead of relying on external host setup/spawning in jenkins clouds. (ENT-5964 TODO)

This is done via an rpm macro.
Build host policy is updated to included needed packages to achieve this. Only on rhel-8.
rhel-9 apparently removed this platform-python as dnf requires python39.

Ticket: ENT-11338
Changelog: title
(cherry picked from commit c307618)

 Conflicts:
	ci/cfengine-build-host-setup.cf

I added all of the build host related files in this commit to 3.21.x as we can track different build host setups eventually to be used in our pipelines instead of relying on external host setup/spawning in jenkins clouds. (ENT-5964 TODO)
@craigcomstock
Copy link
Contributor Author

@cf-bottom jenkins please

@cf-bottom
Copy link

@craigcomstock craigcomstock merged commit 2f488fc into cfengine:3.21.x Feb 20, 2024
37 of 38 checks passed
@craigcomstock craigcomstock deleted the ENT-11338/3.21 branch February 20, 2024 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants