custom copr project not working
See original GitHub issueWhen triggering packit copr-build with project specified, it sets the project name to something else - dhodovsk/packit-cli-hello-world-master and then fails with ERROR Request wasn't successful, there is probably a bug in the API code.
Packit config
[dhodovsk@shiny hello-world]$ cat .packit.yaml
---
specfile_path: hello.spec
jobs:
- job: copr_build
trigger: pull_request
owner: dhodovsk
project: packit
metadata:
targets:
- fedora-all
First copr run:
[dhodovsk@shiny hello-world]$ packit copr-build
Packit 0.8.1 is being used.
Input is a directory: /home/dhodovsk/repos/github.com/packit-service/hello-world
Input directory is an upstream repository.
SRPM is /home/dhodovsk/repos/github.com/packit-service/hello-world/hello-0.72-1.fc30.src.rpm
Copr project dhodovsk/packit-cli-hello-world-master not found. Creating new.
ERROR Request wasn't successful, there is probably a bug in the API code.
Unexpected exception occurred,
please fill an issue here:
https://github.com/packit-service/packit/issues
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
User Documentation — COPR documentation - Pagure.io
We keep one build for each package in one project indefinitely. All other builds (old packages, failed builds) are deleted after 14 days....
Read more >Building modules in Copr - Fedora Documentation
Navigate to a Copr project in a web browser, see the Modules page, and open detail of a module that is to be...
Read more >PR#185: Custom build source method - copr/copr - Pagure.io
I am curious about the added value here. This method will work for every package out there, without ever touching existing git repo...
Read more >Need help creating a package in copr : r/Fedora - Reddit
rpkg build project-name --spec file.spec. Again, you need to setup a few things before these two commands work, but it's not difficult.
Read more >How to handle package dependencies for some build targets ...
I have not yet created the copr project. ... some of the build targets while needs an additional custom repo for some other...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think the precedence should be:
--project
valuecopr_build
jobproject
value from configpackit-cli-{repo_name}-{branch/commit}
we’re IMHO missing 2.
oki, so it seems that we are not reading or using the config value, didn't notice that
And is using of the config value the expected behaviour in the case of CLI? Due to the docs, there is no relation between job config and packit CLI. Also in the command help string, there is nothing about config:@click.option( "--project", help="Project name to build in. Will be created if does not exist. " "(defaults to 'packit-cli-{repo_name}-{branch/commit}')", )