No edit summary |
|||
Line 14: | Line 14: | ||
* '''FIXME''' what is command to do this? | * '''FIXME''' what is command to do this? | ||
<pre> | <pre> | ||
pungi -c /srv/pungi/spin-kickstarts/fedora-install-fedora.ks \ | $ pungi -c /srv/pungi/spin-kickstarts/fedora-install-fedora.ks \ | ||
--destdir /srv/pungi/raw22.0 \ | --destdir /srv/pungi/raw22.0 \ | ||
--cachedir /srv/pungi/cache \ | --cachedir /srv/pungi/cache \ | ||
Line 22: | Line 22: | ||
5) rsync the output, minus the packages and repodata, to alt.fedoraproject.org | 5) rsync the output, minus the packages and repodata, to alt.fedoraproject.org | ||
<pre> | <pre> | ||
rsync -avHh --progress --stats --exclude Packages \ | $ rsync -avHh --progress --stats --exclude Packages \ | ||
--exclude repodata --exclude repoview \ | --exclude repodata --exclude repoview \ | ||
/srv/pungi/raw22.0/development/ \ | /srv/pungi/raw22.0/development/ \ |
Revision as of 02:06, 23 January 2010
Description
From time to time the Quality Assurance team requests official images for testing. Release Engineering is responsible for creating them.
Action
1) Log into compose system (compose-x86-01)
2) Update the compose kickstart file in in the git repo in /srv/pungi/spin-kickstarts/
- FIXME:something here doesn't sound right. What is the full path to the git repo? Copy the updated kickstart file from the git repo to /srv/pungi/spin-kickstarts/ ?
3) Update / create chroots (fedora-devel-compose-{i386,x86_64}
- FIXEME: what are the commands to do this?
4) shell into the chroot
- FIXME what is command to do this?
$ pungi -c /srv/pungi/spin-kickstarts/fedora-install-fedora.ks \ --destdir /srv/pungi/raw22.0 \ --cachedir /srv/pungi/cache \ --nosource \ --nodebug --ver development -GCB
5) rsync the output, minus the packages and repodata, to alt.fedoraproject.org
$ rsync -avHh --progress --stats --exclude Packages \ --exclude repodata --exclude repoview \ /srv/pungi/raw22.0/development/ \ secondary1:/srv/pub/alt/stage/rawhide-yyyymmdd/
6) Update the Release Engineering ticket with the path to the content
Verification
- FIXME: what are the verification steps?
Consider Before Running
- FIXME: What should we include here?