#3378 Option to select spec file for SCM build
Opened 2 years ago by cappyishihara. Modified 2 years ago

Ultramarine Linux uses a Git organization structure on GitHub where all package sources are prefixed by pkg-. This causes some issues with Koji where usually Koji will only build when the spec file is the same name as the Git repo.

We currently have a hack where we use our internal build tool to rename the file to the same as the repo name then build it, but this still causes conflicts with plugins such as rpmautospec.

Adding an option to select a specific spec file in the Git repository like Copr will fix this issue, and also allow usage of monorepos for spec files.


I'm not against. It could be passed as an option to build task. Anyway, it will not fix e.g. rpmautospec issue nor any other plugin expectations about layout. We're not sending spec file information to them (but we can as part of this issue), so they're deciding on their own what is the correct spec.

@mikem any concerns about introducing such option? I would allow this behaviour based on
hub's option (aka canonical_specfile=False) which would be used inside build handler. So, admin can create anything via makeTask but regular dev would be limited by this option. Builder will take anything coming in opts['specfile'] and also pass it to postSCMCheckout dict.

Metadata Update from @tkopecek:
- Custom field Size adjusted to None

2 years ago

Login to comment on this ticket.

Metadata