From Fedora Project Wiki
(Created page with '== Description == From time to time the Quality Assurance team requests official images for testing. Release Engineering is responsible for creating them. == Action == 1) Log i...') |
No edit summary |
||
| Line 10: | Line 10: | ||
4) shell into the chroot | 4) shell into the chroot | ||
<pre> | |||
pungi -c /srv/pungi/spin-kickstarts/fedora-install-fedora.ks \ | |||
--destdir /srv/pungi/raw22.0 \ | |||
--cachedir /srv/pungi/cache \ | |||
--nosource \ | |||
--nodebug --ver development -GCB | |||
</pre> | |||
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> | ||
| Line 21: | Line 22: | ||
--exclude repodata --exclude repoview \ | --exclude repodata --exclude repoview \ | ||
/srv/pungi/raw22.0/development/ \ | /srv/pungi/raw22.0/development/ \ | ||
secondary1:/srv/pub/alt/stage/rawhide- | secondary1:/srv/pub/alt/stage/rawhide-yyyymmdd/ | ||
</pre> | |||
6) Update the Release Engineering ticket with the path to the content | 6) Update the Release Engineering ticket with the path to the content | ||
Revision as of 01:59, 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 compose ks git repo in /srv/pungi/spin-kickstarts/
3) Update / create chroots (fedora-devel-compose-{i386,x86_64}
4) shell into the chroot
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?