Source string Read only

(itstool) path: row/entry

99/990
Context English State
<prompt>#</prompt> <userinput>cd /releng/scripts-snapshot/scripts</userinput>
<prompt>#</prompt> <userinput>./setrev.sh -b <literal>stable/<replaceable>12</replaceable>/</literal></userinput>
<prompt>#</prompt> <userinput>./zfs-cleanup.sh -c ./builds-<replaceable>12</replaceable>.conf</userinput>
<prompt>#</prompt> <userinput>./thermite.sh -c ./builds-<replaceable>12</replaceable>.conf</userinput>
Once the builds have completed, additional helper scripts are available to generate development snapshot emails which are sent to the <literal>freebsd-snapshots@freebsd.org</literal> mailing list:
<prompt>#</prompt> <userinput>cd /releng/scripts-snapshot/scripts</userinput>
<prompt>#</prompt> <userinput>./get-checksums.sh -c ./builds-<replaceable>12</replaceable>.conf | ./generate-email.pl &gt; snapshot-<replaceable>12</replaceable>-mail</userinput>
The generated output should be double-checked for correctness, and the email itself should be PGP signed, in-line.
These helper scripts only apply to development snapshot builds. Announcements during the release cycle (excluding the final release announcement) are created from an email template. A sample of the email template currently used can be found <link xlink:href="https://svn.freebsd.org/base/user/gjb/thermite/non-release-template-mail.txt">here</link>.
Building FreeBSD Releases
Similar to building FreeBSD development snapshots, <filename>thermite.sh</filename> would be invoked the same way. The difference between development snapshots and release builds, <literal>BETA</literal> and <literal>RC</literal> included, is that the <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> configuration files must be named with <literal>release</literal> instead of <literal>snap</literal> as the "type", as mentioned above.
In addition, the <literal>BUILDTYPE</literal> and <literal>types</literal> must be changed from <literal>snap</literal> to <literal>release</literal> in <filename>defaults-<replaceable>12</replaceable>.conf</filename> and <filename>builds-<replaceable>12</replaceable>.conf</filename>, respectively.
When building <literal>BETA</literal>, <literal>RC</literal>, and the final <literal>RELEASE</literal>, also statically set <literal>BUILDSVNREV</literal> to the revision on the branch reflecting the name change, <literal>BUILDDATE</literal> to the date the builds are started in <literal>YYYYMMDD</literal> format. If the <literal>doc/</literal> and <literal>ports/</literal> trees have been tagged, also set <literal>PORTBRANCH</literal> and <literal>DOCBRANCH</literal> to the relevant tag path in the Subversion repository, replacing <literal>HEAD</literal> with the last changed revision. Also set <literal>releasesrc</literal> in <filename>builds-<replaceable>12</replaceable>.conf</filename> to the relevant branch, such as <literal>stable/<replaceable>12</replaceable>/</literal> or <literal>releng/<replaceable>12.0</replaceable>/</literal>.
During the release cycle, a copy of <filename>CHECKSUM.SHA512</filename> and <filename>CHECKSUM.SHA256</filename> for each architecture are stored in the FreeBSD Release Engineering Team internal repository in addition to being included in the various announcement emails. Each <filename>MANIFEST</filename> containing the hashes of <filename>base.txz</filename>, <filename>kernel.txz</filename>, etc. are added to <package>misc/freebsd-release-manifests</package> in the Ports Collection, as well.
In preparation for the release build, several files need to be updated:
Update the <varname>BRANCH</varname> value to <literal>RELEASE</literal>
<filename>UPDATING</filename>
Add the anticipated announcement date
<filename>lib/csu/common/crtbrand.c</filename>
Replace <literal>__FreeBSD_version</literal> with the value in <filename>sys/sys/param.h</filename>
After building the final <literal>RELEASE</literal>, the <literal>releng/<replaceable>12.0</replaceable>/</literal> branch is tagged as <literal>release/<replaceable>12.0.0</replaceable>/</literal> using the revision from which the <literal>RELEASE</literal> was built. Similar to creating the <literal>stable/<replaceable>12</replaceable>/</literal> and <literal>releng/<replaceable>12.0</replaceable>/</literal> branches, this is done with <command>svn cp</command>. From the repository root:
<prompt>%</prompt> <userinput>svn cp ^/<literal>releng/<replaceable>12.0</replaceable>/</literal>@r<replaceable>306420</replaceable> <literal>release/<replaceable>12.0.0</replaceable>/</literal></userinput>
<prompt>%</prompt> <userinput>svn commit <literal>release/<replaceable>12.0.0</replaceable>/</literal></userinput>
Publishing FreeBSD Installation Media to Project Mirrors
This section describes the procedure to publish FreeBSD development snapshots and releases to the Project mirrors.
Staging FreeBSD Installation Media Images
Staging FreeBSD snapshots and releases is a two part process:
Creating the directory structure to match the hierarchy on <systemitem>ftp-master</systemitem>
If <literal>EVERYTHINGISFINE</literal> is defined in the build configuration files, <filename>main.conf</filename> in the case of the build scripts referenced above, this happens automatically in the <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> after the build is complete, creating the directory structure in <filename class="directory">${DESTDIR}/R/ftp-stage</filename> with a path structure matching what is expected on <systemitem>ftp-master</systemitem>. This is equivalent to running the following in the <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> directly:
<prompt>#</prompt> <userinput>make -C /usr/src/release -f Makefile.mirrors EVERYTHINGISFINE=1 ftp-stage</userinput>
After each architecture is built, <filename>thermite.sh</filename> will <application>rsync</application> the <filename class="directory">${DESTDIR}/R/ftp-stage</filename> from the build <citerefentry><refentrytitle>chroot</refentrytitle><manvolnum>8</manvolnum></citerefentry> to <filename class="directory">/snap/ftp/snapshots</filename> or <filename class="directory">/snap/ftp/releases</filename> on the build host, respectively.
Copying the files to a staging directory on <systemitem>ftp-master</systemitem> before moving the files into <filename class="directory">pub/</filename> to begin propagation to the Project mirrors
Once all builds have finished, <filename class="directory">/snap/ftp/snapshots</filename>, or <filename class="directory">/snap/ftp/releases</filename> for a release, is polled by <systemitem>ftp-master</systemitem> using <application>rsync</application> to <filename class="directory">/archive/tmp/snapshots</filename> or <filename class="directory">/archive/tmp/releases</filename>, respectively.
On <systemitem>ftp-master</systemitem> in the FreeBSD Project infrastructure, this step requires <literal>root</literal> level access, as this step must be executed as the <literal>archive</literal> user.
Publishing FreeBSD Installation Media
Once the images are staged in <filename class="directory">/archive/tmp/</filename>, they are ready to be made public by putting them in <filename class="directory">/archive/pub/FreeBSD</filename>. In order to reduce propagation time, <citerefentry><refentrytitle>pax</refentrytitle><manvolnum>1</manvolnum></citerefentry> is used to create hard links from <filename class="directory">/archive/tmp</filename> to <filename class="directory">/archive/pub/FreeBSD</filename>.

Loading…

User avatar None

New source string

FreeBSD Doc / articles_freebsd-relengEnglish

New source string 3 months ago
Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment

(itstool) path: row/entry

Flags
read-only
Source string location
article.translate.xml:1401
String age
3 months ago
Source string age
3 months ago
Translation file
articles/freebsd-releng.pot, string 271