Difference between revisions of "Buildbot"
From Apache OpenOffice Wiki
(→Allocation: adding ppc mac and build type info) |
m (→Platform Coverage: fix spelling) |
||
| (44 intermediate revisions by 9 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | The buildbots are hosted by the Apache Software Foundation at | |
| − | '''http:// | + | '''http://ci.apache.org/projects/openoffice/''' |
| + | The buildbot system used is [http://docs.buildbot.net/current/index.html extensively documented]. | ||
| − | + | The buildbot is a system to automate the compile/test cycle required by most software projects to validate code changes. With automatic and frequent builds, build problems can be pinpointed quickly, before other developers are inconvenienced by the failure. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. | |
| − | + | ==Clean and Incremental Builds== | |
| + | There are two different types of builds: incremental and clean. Incremental builds only compile files that have been changed since | ||
| + | the last build and reuse object files and libraries of unmodified files where possible. Clean builds start with removing old build artifacts from the last build. Clean builds take more time to finish than incremental builds. They are necessary after incompatible changes to the code. A code change is considered incompatible when it affects files for which the build system does not have a dependency on the modified file. | ||
| − | + | ==Nightly and Snapshot Builds== | |
| + | The buildbot performs a daily build, also called "nightly build", of the latest revision of trunk. A snapshot build is done once per week for a fixed revision of trunk or one of the branches. | ||
| − | + | ===Nightly Builds=== | |
| + | Nightly builds are built only for en-US. Installation sets produced by the nightly builds can be found [http://ci.apache.org/projects/openoffice here]. Direct links for the platforms: | ||
| + | *[http://ci.apache.org/projects/openoffice/#linux64 Linux 64bit] | ||
| + | *[http://ci.apache.org/projects/openoffice/#win Windows (32bit)] | ||
| + | * (currently out of order) [http://ci.apache.org/projects/openoffice/#linux32 Linux 32bit] | ||
| − | + | Make sure to check if the build is up to date by looking at the [http://ci.apache.org/projects/openoffice overview]. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | == | + | ===Snapshot Builds=== |
| − | + | Snapshot builds are made for these languages: | |
| − | + | ar cs da de en-GB en-US es fi fr gd gl hu it ja km ko nb nl pt-BR ru sk sl zh-CN zh-TW | |
| − | + | and platforms: | |
| − | + | Windows | |
| − | + | Installation sets produced by the latest snapshot build can be found [https://cwiki.apache.org/confluence/display/OOOUSERS/Development+Snapshot+Builds here]. | |
| − | + | Changing the revision of the snapshot build is run is done by changing the SVN tag named SNAPSHOT: | |
| − | + | *Remove the existing tag: | |
| + | : <code>svn rm https://svn.apache.org/repos/asf/openoffice/tags/SNAPSHOT</code> | ||
| + | *Set the new tag to the desired revision: | ||
| + | : <code>svn copy -r<revision> https://svn.apache.org/repos/asf/openoffice/<trunk-or-branch> https://svn.apache.org/repos/asf/openoffice/tags/SNAPSHOT</code> | ||
| − | == | + | ==Platform Coverage== |
| − | + | The buildbot coverage differs from platform to platform: | |
| + | ;Linux 64bit: The nightly build is always a clean build. There are no general known problems with the Linux 64bit builds. | ||
| + | ;Linux 32bit: Currently out of order (due to hardware problems?) | ||
| + | ;Windows: Clean builds are not reliable. The exact reasons are not yet known, symptoms are missing header files such as apr.h. | ||
| + | Nightly builds are incremental builds by default. | ||
| + | Once a week the nightly build is cleaned. | ||
| + | Clean builds can be requested manually (how?). | ||
| + | ;Mac: At the moment there are no Mac builds because there is no suitable server for this platform. | ||
| − | + | ==Buildbot Configuration File== | |
| + | The [https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/openofficeorg.conf buildbot configuration file] | ||
| + | is available and changable by every committer. | ||
| − | + | [[Category:Build_System]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Revision as of 14:50, 15 April 2013
The buildbots are hosted by the Apache Software Foundation at http://ci.apache.org/projects/openoffice/ The buildbot system used is extensively documented.
The buildbot is a system to automate the compile/test cycle required by most software projects to validate code changes. With automatic and frequent builds, build problems can be pinpointed quickly, before other developers are inconvenienced by the failure. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not.
Contents
Clean and Incremental Builds
There are two different types of builds: incremental and clean. Incremental builds only compile files that have been changed since the last build and reuse object files and libraries of unmodified files where possible. Clean builds start with removing old build artifacts from the last build. Clean builds take more time to finish than incremental builds. They are necessary after incompatible changes to the code. A code change is considered incompatible when it affects files for which the build system does not have a dependency on the modified file.
Nightly and Snapshot Builds
The buildbot performs a daily build, also called "nightly build", of the latest revision of trunk. A snapshot build is done once per week for a fixed revision of trunk or one of the branches.
Nightly Builds
Nightly builds are built only for en-US. Installation sets produced by the nightly builds can be found here. Direct links for the platforms:
- Linux 64bit
- Windows (32bit)
- (currently out of order) Linux 32bit
Make sure to check if the build is up to date by looking at the overview.
Snapshot Builds
Snapshot builds are made for these languages:
ar cs da de en-GB en-US es fi fr gd gl hu it ja km ko nb nl pt-BR ru sk sl zh-CN zh-TW
and platforms:
Windows
Installation sets produced by the latest snapshot build can be found here.
Changing the revision of the snapshot build is run is done by changing the SVN tag named SNAPSHOT:
- Remove the existing tag:
- Set the new tag to the desired revision:
-
svn copy -r<revision> https://svn.apache.org/repos/asf/openoffice/<trunk-or-branch> https://svn.apache.org/repos/asf/openoffice/tags/SNAPSHOT
Platform Coverage
The buildbot coverage differs from platform to platform:
- Linux 64bit
- The nightly build is always a clean build. There are no general known problems with the Linux 64bit builds.
- Linux 32bit
- Currently out of order (due to hardware problems?)
- Windows
- Clean builds are not reliable. The exact reasons are not yet known, symptoms are missing header files such as apr.h.
Nightly builds are incremental builds by default. Once a week the nightly build is cleaned. Clean builds can be requested manually (how?).
- Mac
- At the moment there are no Mac builds because there is no suitable server for this platform.
Buildbot Configuration File
The buildbot configuration file is available and changable by every committer.
