Continuous Build: Difference between revisions

Jump to navigation Jump to search

Continuous Build (edit)

Revision as of 03:34, 22 September 2020

1,655 bytes added ,  22 September 2020
→‎Systems and Configurations
No edit summary
(17 intermediate revisions by 4 users not shown)
Line 1: Line 1:
We use both [http://buildbot.net/ Buildbot] and [http://nixos.org/hydra/ Hydra] to perform continuous building and testing of Octave.
GNU Octave uses [https://buildbot.net/ Buildbot] to build and test the current development version on multiple systems in a number of different configurations.


= Buildbot =
{{Note|The current status of the builds may be found at http://buildbot.octave.org:8010/#/waterfall.}}


We are using [http://buildbot.net/ Buildbot] to build the current development version of Octave on multiple systems in a number of different configurations.  Current status of the builds my be found at [http://buildbot.octave.org:8010/waterfall buildbot.octave.org:8010/waterfall].
= Systems and Configurations =


== Systems and Configurations ==
The following systems and configurations are currently covered for Octave builds:


The following systems and configurations are currently covered:
{| class="wikitable"
|-
! Builder ID !! Hg Version !! System !! Compiler !! Build Options !! Frequency
|-
| clang-4.0-debian || default || Debian Testing || Clang 4.0 || || Any Change
|-
| stable-clang-4.0-debian || stable || Debian Testing || Clang 4.0 || || Any Change
|-
| clang-5.0-debian || default || Debian Testing || Clang 5.0 || || Any Change
|-
| stable-clang-5.0-debian || stable || Debian Testing || Clang 5.0 || || Any Change
|-
| clang-fedora || default || Fedora (current release) || Clang (system default) || || Any Change
|-
| stable-clang-fedora || stable || Fedora (current release) || Clang (system default) || || Any Change
|-
| clang-osx (currently inactive) || default || OS X || Clang || || Any Change
|-
| gcc-7-debian || default || Debian Testing || GCC 7 || || Any Change
|-
| gcc-7-lto-debian || default || Debian Testing || GCC 7 || Enable link time optimization || Any Change
|-
| gcc-fedora || default || Fedora (current release) || GCC (system default) || || Any Change
|-
| gcc-lto-fedora || default || Fedora (current release) || GCC (system default) || Enable link time optimization || Any Change
|-
| no-extras-debian || default || Debian Testing || GCC (system default) || Disable all optional dependencies || Any Change
|-
| stable-no-extras-debian || stable || Debian Testing || GCC (system default) || Disable all optional dependencies || Any Change
|-
|}
 
And for mxe-octave:


{| class="wikitable"
{| class="wikitable"
|-
|-
! Builder ID !! Component !! Hg Version !! Build System !! Host System !! Compiler !! Build Options !! Frequency
! Builder ID !! Hg Version !! Build System !! Host System !! Compiler !! Build Options !! Frequency
|-
|-
| clang-3.7-debian || Octave || default || Debian Testing || Debian || Clang 3.8 || Disable GraphicsMagick || Any Change
| mxe-native-all-on-debian || default || Debian Testing || Debian || GCC (mxe-octave default) || GNU Linux, build all dependencies || Daily
|-
|-
| clang-3.8-debian || Octave || default || Debian Testing || Debian || Clang 3.8 || Disable GraphicsMagick || Any Change
| mxe-native-on-debian || default || Debian Testing || Debian || GCC (system default) || GNU Linux, use system compiler, fontconfig, and X11 libraries || Daily
|-
|-
| clang-3.9-debian || Octave || default || Debian Testing || Debian || Clang 3.8 || Disable GraphicsMagick || Any Change
| w32-on-debian || default || Debian Testing || Windows || GCC (mxe-octave default) || Windows 32 || Daily
|-
|-
| gcc-4.9-debian || Octave || default || Debian Testing || Debian || GCC 4.9 || || Any Change
| w32-stable-on-debian || stable || Debian Testing || Windows || GCC (mxe-octave default) || Windows 32 || Daily
|-
|-
| gcc-5-debian || Octave || default || Debian Testing || Debian || GCC 5 || || Any Change
| w32-release-on-debian || release (tarball) || Debian Testing || Windows || GCC (mxe-octave default) || Windows 32 || Daily
|-
|-
| gcc-6-debian || Octave || default || Debian Testing || Debian || GCC 6 || Disable GraphicsMagick || Any Change
| w64-32-on-debian || default || Debian Testing || Windows || GCC (mxe-octave default) || Windows 64 || Daily
|-
|-
| gcc-6-lto-debian || Octave || default || Debian Testing || Debian || GCC 6 || Enable link time optimization, Disable GraphicsMagick || Any Change
| w64-32-stable-on-debian || stable || Debian Testing || Windows || GCC (mxe-octave default) || Windows 64 || Daily
|-
|-
| no-extras-debian || Octave || default || Debian Testing || Debian || Clang 3.8 || Disable all optional dependencies || Any Change
| w64-32-release-on-debian || release (tarball) || Debian Testing || Windows || GCC (mxe-octave default) || Windows 64 || Daily
|-
|-
| w32-on-debian || mxe-octave || default || Debian Testing || Windows || GCC || Windows 32 || Daily
| w64-64-on-debian || default || Debian Testing || Windows || GCC (mxe-octave default) || Windows 64, 64-bit indexing || Daily
|-
|-
| w64-32-on-debian || mxe-octave || default || Debian Testing || Windows || GCC || Windows 64 || Daily
| w64-64-stable-on-debian || stable || Debian Testing || Windows || GCC (mxe-octave default) || Windows 64, 64-bit indexing || Daily
|-
| w64-64-release-on-debian || release (tarball) || Debian Testing || Windows || GCC (mxe-octave default) || Windows 64, 64-bit indexing || Daily
|-
|-
| w64-64-on-debian || mxe-octave || default || Debian Testing || Windows || GCC || Windows 64, 64-bit indexing || Daily
|}
|}


If you are interested in maintaining a buildbot slave for a different configuration, please contact the [mailto:octave-maintainers@gnu.org Octave Maintainers] mailing list.
= Setup and run a Buildbot Worker =
 
Your system may be behind a firewall.  It does not have to have a distinct public IP address.
 
To support Octave development and run a Buildbot Worker, you must do the following:


= Hydra =
* Contact the [https://octave.discourse.group/c/maintainers/7 Octave Maintainers on Discourse] to let us know that you wish to provide a system to use as a Buildbot Worker.  We will give you a <code>WORKERNAME</code> and a '''secret''' <code>PASSWORD</code> to configure your Buildbot Worker.
* Install buildbot.  Packages exist for most distributions.  See the buildbot docs for other options.  You should create a separate user account with no special privileges that will run buildbot.
* Decide for a <code>BASEDIR</code>.  For example, if the home directory for the buildbot user is {{Path|/var/lib/buildbot}} and your <code>WORKERNAME</code> is set to <code>'debian-x86_64'</code> , then <code>BASEDIR</code> might be {{Path|/var/lib/buildbot/worker/debian-x86_64}}.
* <code>MASTERHOST</code> is <code>buildbot.octave.org</code> and <code>PORT</code> is <code>9989</code>.
* Create the configuration<pre>buildbot-worker create-worker BASEDIR MASTERHOST:PORT WORKERNAME PASSWORD</pre>
* Run buildbot on the worker system, preferably by starting it automatically when your system boots.  It should be running with the buildbot user ID. <pre>buildbot-worker start BASEDIR</pre>


There is a build server continuously building the latest tip of the development branch of Octave. The build server is running [http://nixos.org/hydra/ Hydra], which is based on the [http://nixos.org/nix/ Nix] functional package management system. This is the official continuous build system of the GNU Project. The Hydra build of Octave is currently maintained by [[User:Mtmiller]].
== ccache ==


== Octave Job Overview ==
You may also want to set up '''ccache''' to work with buildbot (strongly recommended to speed up builds).  If you create a directory {{Path|~/buildbot/bin}}, it will be added to the execution PATH when the Buildbot Master runs commands on the Buildbot Worker.  This directory can have symbolic links like the following:


The [http://hydra.nixos.org/jobset/gnu/octave-default octave-default jobset overview] page is the main entry point to the Hydra build of Octave. It shows the status of the most recent builds ("evaluations" in Hydra terminology).
cc      -> /usr/bin/ccache
c++      -> /usr/bin/ccache
gcc      -> /usr/bin/ccache
gfortran -> /usr/bin/ccache


== Latest Build Logs ==
They should point to the actual location of ccache if it is not in {{Path|/usr/bin}}.


The full build logs for the latest builds are available at the following links, for quick reference:
== Space Requirements ==


* [http://hydra.nixos.org/job/gnu/octave-default/tarball/latest/log/raw Tarball]
Building Octave takes a significant amount of disk space. With debugging symbols, you may need several GB for each build, plus room for ccache (possibly 50GB) if you use it. If you use a cache size that is larger than the default, you'll need to specify that in the {{Path|.ccache/ccache.conf}} file using a line like
* [http://hydra.nixos.org/job/gnu/octave-default/build.x86_64-linux/latest/log/raw Linux x86_64]
* [http://hydra.nixos.org/job/gnu/octave-default/build.i686-linux/latest/log/raw Linux i686]
* [http://hydra.nixos.org/job/gnu/octave-default/coverage/latest/log/raw Coverage]


== Snapshot Source Tarball ==
max_size = 50G


A nice product of the Hydra continuous build of Octave is that there is always a [http://hydra.nixos.org/job/gnu/octave-default/tarball/latest/download source snapshot] available for download. This source snapshot is always built from the current tip of the development branch in whatever state it is in. Therefore, it may not compile or run properly and should definitely not be used for anything other than evaluation. This can be useful to evaluate the current state of Octave's development branch without needing to clone the Mercurial repository.
If the directory containing the build and ccache directories doesn't have sufficient space, then these directory names may point to a separate partition that does have enough space available.


== Coverage Report ==
= External links =


Another product of the Hydra continuous build is the [http://hydra.nixos.org/job/gnu/octave-default/coverage/latest/download code coverage report]. The latest coverage report is always built from the current tip of the development branch. This report gives an analysis of the code coverage of the current Octave test suite. This can be used to find unexercised code paths and help improve the coverage of Octave's test suite (see [[Projects#Tests]]).
* [https://hg.octave.org/octave-buildbot/ Buildbot configuration repository] for http://buildbot.octave.org:8010


[[Category:Development]]
[[Category:Building]]
Anonymous user
Retrieved from "https://wiki.octave.org/Special:MobileDiff/9546...13347"

Navigation menu