Bug 1696468

Summary: RFE: build-and-download command
Product: [Fedora] Fedora Reporter: Van de Bugger <van.de.bugger>
Component: copr-cliAssignee: Miroslav Suchý <msuchy>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: clime, dturecek, imvalgo, jkadlcik, msuchy, praiskup
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-15 06:02:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Van de Bugger 2019-04-04 22:07:49 UTC 
Version-Release number of selected component (if applicable):

copr-cli-1.78-1.fc29.noarch


Description of problem:
=======================

I want to build a source rpm in COPR *and* download binary rpms from COPR to the local system. I can easily build a source rpm with copr tool:

$ copr build USER/PROJECT SRPM

copr tool has a command to download the build, but I have to specify build id in order to download the build:

$ copr download-build BUILD-ID

To find out BUILD-ID, I have to parse "copr build" output, it is not convenient. It would be nice if copr tool has build-and-download command, e. g.:

$ copr build-and-download USER/PROJECT SRPM

Alternatively, build command can save build id in a file, so it can be used without parsing the command output, e. g.:

$ copr build --save-build-id-to-file=id.txt USER/PROJECT SRPM

so the next command could be:

$ copr download-build $(<id.txt)
Comment 1 Jakub Kadlčík 2019-04-05 08:06:32 UTC 
Thank you for the feedback,


> Alternatively, build command can save build id in a file, so it can be used without parsing the command output, e. g.:


Similar RFE was already discussed in this issue https://pagure.io/copr/copr/issue/224 but wasn't implemented yet. You may want to join the discussion.
Comment 2 Pavel Raiskup 2019-04-15 06:02:58 UTC 
Agreed, I interlinked the upstream issue too and we can move there then, to 
avoid duplicate reports.  Thanks for the report!