Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1055663 - RFE: Create/Store/Use list of builds to be pushed
Summary: RFE: Create/Store/Use list of builds to be pushed
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: bodhi
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Patrick Uiterwijk
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-20 17:47 UTC by David Aquilina
Modified: 2016-10-18 15:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-18 15:26:59 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Github fedora-infra bodhi pull 1011 None None None 2016-10-18 15:26:59 UTC

Description David Aquilina 2014-01-20 17:47:33 UTC
Description of problem:

Currently, the process to push Fedora updates works like this: 

1) Run "bodhi -P --push-release F20", then say no at the 'Push these updates?' confirmation. This creates Stable-F20 and Testing-F20 files with a list of NVRs.

2) Use the Stable-F20 and Testing-F20 files as input to sigul to sign the packages, with "sigulsign_unsigned.py -v --write-all fedora-20 $(cat Stable-F20 Testing-F20)"

3) Re-run the bodhi command from step 1, **and hope that nobody has created new updates while you were signing**. If new updates have been created you have to once again say 'no', sign the new list of NVRs, then try again. 

It would make life easier if bodhi could use the list of NVRs it created in Step 1 as the basis for the push after they've been signed. We often have to repeat these steps many times before we get all the updates in step 3 signed without new updates being created.

Comment 2 Randy Barlow 2016-10-18 15:26:59 UTC
I believe that the incredible puiterwijk has solved this problem for us! It should appear in the upcoming 2.3.0 release.


Note You need to log in before you can comment on or make changes to this bug.