Code Monkey home page Code Monkey logo

Comments (3)

lubomir avatar lubomir commented on August 24, 2024

nightly is a compose type, which is orthogonal to release type.

Why not use ga? Why should the fact that the base product is not released yet change anything?

Alternatively, can you check release_type in a compose of the base product? I think you should use the same value.

from productmd.

ktdreyer avatar ktdreyer commented on August 24, 2024

re: why not use ga? Good question, I should explain more.

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 gather_lookaside_repos setting from Pungi's config-dump JSON, because that will differ between RHEL GA and a RHEL pre-release. It will even give me the exact URLs Pungi used for repoclosure.

I'm just brainstorming at this point. I was just wondering about your thoughts regarding whether it makes sense to put this into productmd.

from productmd.

lubomir avatar lubomir commented on August 24, 2024

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 pre_release, but I see a few issues.

  • Even the pre-release composes of RHEL will have release type set to ga, so there will never be an actual compose of a pre-release product marked as such.

  • Another issue is that base product type is reflected in release ID. So now you would be composing ceph-3.0@rhel-7-pre_release, and once the base product is actually released, your release ID would change to ceph-3.0@rhel-7. For example from Product Definition Center point-of-view those will be different releases.

from productmd.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.