Description
When Quality Engineering requests a TC or RC they do so by filing or reopening a ticket in Release Engineering trac. There is one trac ticket per milestone.
Action
create the full product tree.
Composing the Tree
1) Log into compose system: compose-x86-02
$ ssh -A compose-x86-02.phx2.fedoraproject.org
ssh agent forwarding is needed to enable sshing to boxes for composing the different arch trees.
2) update or checkout the git repo
$ cd releng/ $ git pull --rebase
or
$ git clone git://git.fedorahosted.org/git/releng
3) Sign rpms for bleed repo
ssh releng04.phx2.fedoraproject.org
repeat step 2 on signing box.
$ cd releng/scripts $ NSS_HASH_ALG_SUPPORT=+MD5 ./sigulsign_unsigned.py fedora-20 -v --write-all <build nvrs>
4) update the bleed repo on compose-x86-02
$ cd ~/bleed $ ~/releng/scripts/makebleed <build nvrs>
5) kick off image composition on localhost
locally checkout spin-kickstarts and cloud-kickstarts git repos
$ git clone ssh://git.fedorahosted.org/git/spin-kickstarts.git $ git clone ssh://git.fedorahosted.org/git/cloud-kickstarts.git
Update the ticket
The ticket should be closed when the compose has been opened up pasting in the output from run-pungi
Verification
Verification can be done as the task steps are being performed.
Image Creation
When pungi exits, you can verify that the development/<arch>/os/images/ directory exists and has content. That path is relative to the destination directory you provide pungi.
Updating the Ticket
One can click the link provided in the ticket update and ensure the path is correct. Verifying that the ticket is closed should be pretty self evident.
Consider Before Running
Many things can hinder a compose, broken deps in the chroot set, broken deps in the compose set, bugs in the compose software, etc... If any problem is ran into along the way, it is best to alert QA via a ticket update, and then work with the appropriate party to clear the obstruction.
Some of these tasks take a long time to finish, so it is highly recommended that you run these tasks in a screen session.
If you need to make use of freshly built packages since the last rawhide compose, you can create a local repository. /srv/pungi/bleed/<arch>/ on the compose system can be used as a temporary repo for new packages. Don't forget to update the mock chroot with the new packages (if appropriate) and to add the temporary repo to the spin-kickstarts/fedora-install-fedora.ks file for use by pungi.
Disk space on secondary1 is limited, so if you need to go through a number of composes before you get one that tests well, be sure to prune the failed composes. This is true of disk space on the compose host too, be sure to trim /srv/pungi/ of composes that are no longer needed locally.