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 RPM support for s390x platform #3202

Closed
cfilleke opened this issue Apr 17, 2024 · 1 comment · Fixed by #3286
Closed

Provide RPM support for s390x platform #3202

cfilleke opened this issue Apr 17, 2024 · 1 comment · Fixed by #3286

Comments

@cfilleke
Copy link
Collaborator

cfilleke commented Apr 17, 2024

Provide RPM support for s390x platform as described in issue #3198
Is your feature request related to a problem? Please describe:
Add support for bazeldnf to maintain the rpm lists for s390x in BUILD.bazel

Describe the solution you'd like:

Add configurations necessary for bazeldnf to generate the rpm lists in WORKSPACE and BUILD.bazel, using the information for how to maintain these lists in .bazelrc, repo.yaml and hack/build/rpm-defs.sh as described in #3089 and #3090

Describe alternatives you've considered:
An alternative approach, which we've also been pursuing, would be to provide all the changes necessary for s390 builds in one PR; there are many moving parts to this, and the CI/CD needs to be installed on an s390x host to test the full set of changes.

Additional context:

Once the CI/CD system for s390x goes live, the full cross-compiled build for s390x CDI can, too.

The strategy we're choosing is to essentially cherry-pick changes that will run and be smoke tested in the x86-based CI/CD system, to reduce the risk when the PR for the full s390x build-and-test system is merged.

@cfilleke
Copy link
Collaborator Author

Suggested Test:

make rpm-deps will conduct a smoke test -- that the additions do not break the build and produce the expected result: rpm list updates in the WORKSPACE file, now with rpms for s390x architecture!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant