Skip to content

DAOS-17203 build: Build DAOS RPMs with Leap 15.6. #460

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

phender
Copy link
Contributor

@phender phender commented Mar 3, 2025

Use the opensuse-leap-15.6-x86_64.cfg mock config to build DAOS RPMs.

Copy link
Contributor

@daltonbohning daltonbohning left a comment

Choose a reason for hiding this comment

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

LGTM but no pipeline-lib testing?

@daltonbohning
Copy link
Contributor

LGTM but no pipeline-lib testing?

Ah, I think GitHub is being funny + Jenkins down

Use the opensuse-leap-15.6-x86_64.cfg mock config to build DAOS RPMs.

Signed-off-by: Phil Henderson <phillip.henderson@hpe.com>
@phender phender force-pushed the hendersp/DAOS-17203 branch from d2749f9 to b97f2df Compare March 3, 2025 20:14
@phender phender requested a review from daltonbohning March 3, 2025 20:25
Signed-off-by: Phil Henderson <phillip.henderson@hpe.com>
@phender
Copy link
Contributor Author

phender commented Mar 6, 2025

The Functional on Leap 15.6 stage failures in the weekly-testing and weekly-2.6-testing branches are due to:

Error: Unable to find a match: daos-2.7.101-5.11126.g864448e5.suse.lp156

Which is because the master and release/2.6 branches do not yet build daos-*.suse.lp56 RPMs until daos-stack/daos#16001 is working (for master) and we have a similar update in the release/2.6 branch.

We really should have the branches control/define the distro versions they use and have pipeline-lib define more generic functions. So I need a way to pass not just the provision distro version to getFunctionalTestStage(), but also the daos distro version - where ideally this inforamtion would come from the base branch (e.g. master or release/x.y) and would not have to be defined/updated in each daily/weekly/provider-testing branch.

Signed-off-by: Phil Henderson <phillip.henderson@hpe.com>
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants