External/fedora-kickstarts
1
0
Fork 0
mirror of https://pagure.io/fedora-kickstarts.git synced 2024-12-22 05:35:26 +00:00
Code Issues Packages Projects Releases Wiki Activity

fedora-atomic: add updates and updates-testing kickstarts

Browse Source 
This is so we can build media during the updates composes using the
updates and or testing refs. They include the base fedora-atomic.ks.
This commit is contained in:
Dusty Mabe 2018-10-11 11:50:15 -04:00
parent 8c83a275ee
commit 899bc45aa1
No known key found for this signature in database
GPG Key ID: 3302DBD73952E671
4 changed files with 70 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
fedora-atomic-testing.ks Normal file
View File

@ -0,0 +1,29 @@
# ./fedora-atomic-testing.ks - for building media from the testing
# refs (fedora/29/${basearch}/testing/atomic-host)
%include fedora-atomic.ks
ostreesetup --nogpg --osname=fedora-atomic --remote=fedora-atomic --url=https://kojipkgs.fedoraproject.org/compose/atomic/repo/ --ref=fedora/29/${basearch}/testing/atomic-host
%post --erroronfail
# Find the architecture we are on
arch=$(uname -m)
# Set the origin to the "main stable ref", distinct from /testing/ which is where bodhi writes.
# We want consumers of this image to track the two week releases.
ostree admin set-origin --index 0 fedora-atomic https://dl.fedoraproject.org/atomic/repo/ "fedora/29/${arch}/atomic-host"
# Make sure the ref we're supposedly sitting on (according
# to the updated origin) exists.
ostree refs "fedora-atomic:fedora/29/${arch}/testing/atomic-host" --create "fedora-atomic:fedora/29/${arch}/atomic-host"
# Remove the old ref so that the commit eventually gets
# cleaned up.
ostree refs "fedora-atomic:fedora/29/${arch}/testing/atomic-host" --delete
# delete/add the remote with new options to enable gpg verification
# and to point them at the cdn url
ostree remote delete fedora-atomic
ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary fedora-atomic 'https://dl.fedoraproject.org/atomic/repo/'
%end

29
fedora-atomic-updates.ks Normal file
View File

@ -0,0 +1,29 @@
# ./fedora-atomic-updates.ks - for building media from the updates
# refs (fedora/29/${basearch}/updates/atomic-host)
%include fedora-atomic.ks
ostreesetup --nogpg --osname=fedora-atomic --remote=fedora-atomic --url=https://kojipkgs.fedoraproject.org/compose/atomic/repo/ --ref=fedora/29/${basearch}/updates/atomic-host
%post --erroronfail
# Find the architecture we are on
arch=$(uname -m)
# Set the origin to the "main stable ref", distinct from /updates/ which is where bodhi writes.
# We want consumers of this image to track the two week releases.
ostree admin set-origin --index 0 fedora-atomic https://dl.fedoraproject.org/atomic/repo/ "fedora/29/${arch}/atomic-host"
# Make sure the ref we're supposedly sitting on (according
# to the updated origin) exists.
ostree refs "fedora-atomic:fedora/29/${arch}/updates/atomic-host" --create "fedora-atomic:fedora/29/${arch}/atomic-host"
# Remove the old ref so that the commit eventually gets
# cleaned up.
ostree refs "fedora-atomic:fedora/29/${arch}/updates/atomic-host" --delete
# delete/add the remote with new options to enable gpg verification
# and to point them at the cdn url
ostree remote delete fedora-atomic
ostree remote add --set=gpg-verify=true --set=gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-primary fedora-atomic 'https://dl.fedoraproject.org/atomic/repo/'
%end

6
fedora-atomic-vagrant-testing.ks Normal file
View File

@ -0,0 +1,6 @@
# ./fedora-atomic-vagrant-testing.ks - for building media from the testing
# refs (fedora/29/${basearch}/testing/atomic-host) for vagrant
%include fedora-atomic-vagrant.ks
%include fedora-atomic-testing.ks

6
fedora-atomic-vagrant-updates.ks Normal file
View File

@ -0,0 +1,6 @@
# ./fedora-atomic-vagrant-updates.ks - for building media from the updates
# refs (fedora/29/${basearch}/updates/atomic-host) for vagrant
%include fedora-atomic-vagrant.ks
%include fedora-atomic-updates.ks