peridot icon indicating copy to clipboard operation
peridot copied to clipboard

peridot module building cli/api mismatch

Open josephtate opened this issue 9 months ago • 0 comments

Describe The Bug

I get 500 errors from the peridot server if I try to specify branches in my --module-variant builds.

Reproduction Steps

  1. Select a module to build
  2. Run peridot build package <module> --module-variant --debug --branches <my branch>
  3. there is no step 3

peridot cli reports the server responded with a 500 error with the message:

{"code":2,"message":"could not find upstream branch","details":[]}

Expected Behavior

Expected is that the tip of the selected branch will be built as a module

Version and Build Information

$ peridot --version
peridot version 9a1a7d42065aa833087a46b07d8789788715e2bf

Installed from RPM peridot-cli-0.2.1-1.x86_64

Additional context

I'm trying to build against a Rocky 8 project, which has a much different module strategy than rocky 9.

Mustafa says, "Instead of trying to detect. The initial detection is just checking PREFIX-MAJOR and it fails too early for packages that are ONLY modules"

josephtate avatar May 16 '24 22:05 josephtate