-
Notifications
You must be signed in to change notification settings - Fork 34
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
more options for BaseProduct.type #93
Comments
Why not use Alternatively, can you check |
re: why not use The purpose of this feature would be to standardize how I indicate my product's test environment. I want to indicate to our QE team and associated test tools that "this compose should be used with a RHEL pre-release". That way, I can point our tools at a compose URL and say "go test this", and the tooling uses productmd to look up what sort of compose it is and what sort of environment it needs. That way I don't need to hardcode decisions like "if release is Ceph 3.0, use RHEL 7.4, otherwise use the latest RHEL GA". Another option I'm considering is to look up the I'm just brainstorming at this point. I was just wondering about your thoughts regarding whether it makes sense to put this into productmd. |
Oh I see, I incorrectly assumed base product version uses the usual MAJOR.MINOR schema. However it's only the major version. So your use case is that both 3.0 and the previous version are based on RHEL-7, but one should use the released version and the other the pre-release version. Correct? We could add a new release_type such as
|
The latest in-development version of my Ceph 3.0 layered product is based on a not-yet-available version of RHEL (7.4).
I was hoping I could specify this in the compose metadata (setting
base_product_type = "nightly"
in my Pungi config), but it looks like we restrictBaseProduct.type
toproductmd.common.RELEASE_TYPES
:What would be the best way to indicate in the compose metadata that my layered product is based on a not-yet-released base product?
The text was updated successfully, but these errors were encountered: