From Fedora Project Wiki

(Created page with '== Description == Fedora updates for released er releases are typically pushed once a work day. This SOP covers the steps involved. == Action == 1. install <code>bodhi-client<...')
 
(Replaced content with "{{admon/important|This page has moved [https://docs.pagure.org/releng/sop_pushing_updates.html here]| All Fedora Release Engineering Documentation has moved [https://docs....")
 
(48 intermediate revisions by 8 users not shown)
Line 1: Line 1:
== Description ==
{{admon/important|This page has moved [https://docs.pagure.org/releng/sop_pushing_updates.html here]| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source hosted along side the code in the [https://pagure.io/releng releng pagure repository]}}
Fedora updates for released er releases are typically pushed once a work day. This SOP covers the steps involved.


== Action ==


1. install <code>bodhi-client</code> on your local workstation
<pre>
yum install <I don't know>
</pre>
2. refresh login cache
<pre>
$ bodhi -m
</pre>
3. Get a list of packages to push
<pre>
$ bodhi -P --push-release F12 --push-release F13
</pre>
{{admon/warning|WAIT!| Do NOT press "Yes" yet.}}
4. Copy build names to signing host, one package name per line
<pre>
'''FIXME'''--commands?
</pre>
5. Sign builds using scripts/sigulsign_unsigned.py from releng git repo
<pre>
$ ./sigulsign_unsigned.py -vv --write-all fedora-13 $(cat tosign)
</pre>
{{admon/caution|Run this process from <code>screen</code>| It is strongly suggested that the above procedure be run from screen.  Doing so requires a host configured as sigul client.  See the sigul client SOP '''NEED LINK'''}}
6. Press yes on bodhi push command.  If prompted for a password CTRL+c and start over.
== Verification ==
1. Tail the bodhi server log to watch progress on releng2:
<pre>
$ sudo tail -f /var/log/bodhi/server.log
</pre>
Wait for the bodhi masher report (sent to bodhi-adminmember@fp.o) for success/failure.
== Consider Before Running ==
Pushes often fall over due to tagging issues or unsigned packages.  Be prepared to work through the failures and restart pushes from time to time
<pre>
$ bodhi -P --resume-push
</pre>
* '''FIXME'''--include a listing common failure cases and how to work around them


[[Category:Release Engineering SOPs]]
[[Category:Release Engineering SOPs]]

Latest revision as of 16:29, 4 April 2016

Important.png
This page has moved here
All Fedora Release Engineering Documentation has moved here with source hosted along side the code in the releng pagure repository
Retrieved from "https://fedoraproject.org/w/index.php?title=Pushing_updates_SOP&oldid=441753"