Uploaded image for project: 'AI Platform Core Components'
  1. AI Platform Core Components
  2. AIPCC-3172

automatically resolve vllm tags to versions

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Accelerator Enablement
    • None
    • automatically resolve vllm tags to versions
    • False
    • Hide

      None

      Show
      None
    • False
    • In Progress
    • 0% To Do, 0% In Progress, 100% Done
    • Hide

      18/August/25 - Green - done

      Show
      18/August/25 - Green - done

      We should use fromager's GitLabTagProvider to automatically turn git repo tags to version numbers for resolving which versions of vllm can build. We should retain the constraints.txt entries to let each variant build a different version, until we can automatically build all new versions.

      It looks like the pattern is to have a midstream/downstream tag that adds an extra digit to the version number (0.8.3 is tagged 0.8.3.0_downstream, for example).

      There is a mix of patterns, like v0.8.4.2_downstream, 0.8.3.0_downstream, midstream-v0.8.5.0, midstream-room-v0.9.0.1.0 today. That last one makes it seem like we need a variant-specific regex, at least to handle some of the cases.

              emacchi@redhat.com Emilien Macchi
              dhellman@redhat.com Doug Hellmann
              Frank's Team
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: