Skip to content

Define architecture for doing both el8 and el9 builds. #102

@ndp-opendap

Description

@ndp-opendap

We have, for the most part, separated the component tagging in our S3 bucket so it's easy to identify el8 vs el9 assists.

In my el9 branch on this repo there are two "build recipe" files, one for el8 and one for el9. The TravisCI (.travis.yml) has a hard coded definition on which to use:

    - BUILD_RECIPE="el9-build-recipe"

That's fine for now but when we merge this all down to the main branch we need to have a way to detect which version of RHEL is being target by the most recent commit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions