-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[copr-dist-git] Don't assume the SCM repo has the same name as the package #1
Conversation
…ckage Mock(-scm) expects the cloned directory to has the same name as the package it's building. To make sure it is so we explicitly pass the package name to git clone as a destination directory name. This allows (amont other things) to have a single git repo for multiple spec files.
Can you provide copr-dist-git import-task description in the following form?
This will represent a test case for which the current codebase fails ( |
Sorry for taking so long:
(or do you want a real-world data? I don't know if I can provide any persistent source data for that). The idea is that package name (which I don't have access to devel.redhat.com anymore, so please integrate it for me :) |
Oki, I understand the problem and I'll make a nice test case out of it :). I meant real-world data that I would encapsulate later but I got the point and found one my own repositories that I can reproduce the problem on (https://github.com/clime/example2 with subpkg/example.spec). Anyway, thank you for the fix and the first pull request! |
[copr-dist-git] Don't assume the SCM repo has the same name as the package
This shouldn't actually normally happen, but just in case (the problem happened once when we had an old copr-rpmbuild package instlaled on builders). The error output would be: Backend process error: Error while collecting built packages for 2134118-fedora-rawhide-x86_64: Worker failed build, took 116.72690773010254 Retry request #1 on https://copr-fe-dev.cloud.fedoraproject.org/backend/update/: Request server error on https://copr-fe-dev.cloud.fedoraproject.org/backend/update/: 500 INTERNAL SERVER ERROR Retry request #2 on https://copr-fe-dev.cloud.fedoraproject.org/backend/update/: Request server error on https://copr-fe-dev.cloud.fedoraproject.org/backend/update/: 500 INTERNAL SERVER ERROR ... While I'm on it, let's move the _parse_results on a slightly better place where the exceptions aren't ignored.
New script #1: /usr/bin/copr-backend-analyze-results Run a 'du' command on the result storage directory and calculate several useful statistics. New script #2: /usr/bin/copr-backend-generate-graphs Go through the results provided by script #1, and generate the interactive graphs. New cron file: /etc/cron.weekly/copr-backend Execute script #1 and then script #2 to update the graphs. Closes: #1739
Mock(-scm) expects the cloned directory to has the same name as the package
it's building. To make sure it is so we explicitly pass the package name to
git clone as a destination directory name.
This allows (amont other things) to have a single git repo for multiple spec
files.