Upgrade Notes

Due to some of the big changes in Buildix 2.1, care needs to be taken when upgrading from 2.0. As always before trying anything big, please make sure you have good backups of your data before trying this.

Upgrade Steps (all as root)

  • Run the command: aptitude update
  • Run the command: aptitude dist-upgrade
  • During the install process, you will be prompted about replacing certain files. They are:
    • /etc/apache2/sites-available/buildix - you should select Y to install the maintainers version
    • /etc/buildix/htpasswd - you should select N to keep your current version.
    • /var/lib/mingle/config/auth_config.yml - you should select Y to install the maintainers version

Passwords

One of the security changes for 2.1 has been that we now store passwords in the /etc/buildix/htpasswd file as SHA hashes instead of the old crypt format. Apache and everything will still work with the old passwords, but we recommend you update existing users passwords using the user manager as soon as possible. Even if you don’t change the password, saving it will write it in the new format.

Mingle

To use the new Mingle API, Buildix needs to have the username and password of a Mingle admin user. If you upgrade, it will try and use the username/password combination of admin/admin, which probably does not match your Mingle installation. To fix this, you need to make sure that the username and password values in your /etc/buildix/buildix.conf file under the [mingle] section match a valid admin account in Mingle. If you don’t want to use Mingle, set mingle=False in the [modules] section of that config file. Note that you also need to connect to your Mingle URL and finish the upgrade process there before you can create new projects.

Ubuntu 7.04

If you’re still running on Ubuntu 7.04 you might have a problem with SSL. If you are getting a connection refused error, you need to do is edit the /etc/apache2/ports.conf file and add a new line reading Listen 443 and then restart Apache.

FAQ

General

Where is all my data kept / what should I back up?

The important directories are:

/var/trac - all your trac projects are here
/var/svn - all your svn repositories are here
/var/spool/cruisecontrol - this is your CruiseControl working directory
/etc/buildix - Buildix configuration
/etc/cruisecontrol - CruiseControl configuration

If you’re using Mingle, the data will be in the Postgres database called mingle, although when logged in as an admin user there is a full import/export feature available.

In general though just treat it as you would any of your other Linux servers…

I’ve just upgraded from 2.0 to 2.1 and now I can’t create projects

To use the new Mingle API, Buildix needs to have the username and password of a Mingle admin user. If you upgrade, it will try and use the username/password combination of admin/admin, which probably does not match your Mingle installation. To fix this, you need to make sure that the username and password values in your /etc/buildix/buildix.conf file under the [mingle] section match a valid admin account in Mingle. If you don’t want to use Mingle, set mingle=False in the [modules] section of that config file.

I get errors after installing Buildix 2.0 under Ubuntu 7.10

Currently the officially supported platform is Ubuntu 7.04. There is a known problem after installation on 7.10. The work around is to either restart Apache and CruiseControl (sudo /etc/init.d/apache2 restart and sudo /etc/init.d/cruisecontrol restart) or reboot the machine. More info at on the forums.

How do I block anonymous access to my SVN repository?

Thanks to Edwin documenting this in the forums here. Please remember to restart Apache for this to take effect.

How do I put some authentication around /usermanager and /projectmanager for public facing installations?

There’s a thread on the forum that covers this.

VMWare Image

How do I change the keyboard map in the VMWare image from UK?

The keyboard layout for the console is defined in the file /etc/default/console-setup. To change it to the US layout, edit the file and change XKBLAYOUT=”gb” to XKBLAYOUT=”us” and then run /etc/init.d/console-setup start

How do I find out what IP address my VMWare image is using?

At the login prompt type in the username ifconfig and just press Enter when asked for the password. This will print out the IP address information for the Virtual Machine.

Is it safe to run the VMWare image with an external IP address?

The Buildix VMWare and ISO images are not secure. They are not meant to be run in any kind of hostile environment. You can run it internet facing, but we recommend you start off with your own secure Ubuntu installation and then just add the Buildix packages.

LiveCD

Why can’t I log in after installing to hard drive from the LiveCD?

There is a bug in the Ubuntu installer which I’ve not been able to track down. During the install process it asks you for a username and password, but then promptly ignores it. A system user used by the LiveCD called buildix (with the password buildix) must be used instead.

AMI Image

I keep getting “perl: warning: Setting locale failed”, how do I stop them?

By default the AMI image sets LANG=en_GB.UTF-8, but it does not have the files to cope with it. Fix this by running locale-gen en_GB.UTF-8.

Download

Repository

The Ubuntu repository root is http://buildix.thoughtworks.com/repos/debian. For more info on using this, please read the Installation notes. Even if you use one of the images below, you will still be using this mechanism to get updates.

Latest Images

Live CD

  • buildix-2.1.iso [torrent] - (659MB) released 2 May 2008
    • md5sum: db10da9031215b268df4b0bf1996866b
    • sha1sum: 2cc8d43f5e2d38a1041a6e4e7cdc2d259f40993f

VMWare Image

Previous Releases

Live CD

  • buildix-2.0.iso [torrent] - (645MB) released 15 October 2007
    • md5sum: 274de55d59fe48f1bc3f1a42d8ecaa42
    • sha1sum: ae1c875ff04069cec4ede22159386c05cd8e2867

VMWare Image

  • buildix-2.0-vmware.tar.bz2 - (504MB) released 19 October 2007
    • md5sum: 625217909759924889ba1a9dbda7a6f0
    • sha1sum: 081b4a8d04604f9736f1cfa2bd0e7d0076032787

Amazon EC2

  • AMI ID: ami-e4ca2f8d - released 15 November 2007

Installation

To install the Buildix 2.1 packages, download and install Ubuntu 7.10. Both Server and Desktop editions are supported. Then do the following on your fresh server as the root user:

  • Edit /etc/apt/sources.list and add the following line to the bottom of the file:
    deb http://buildix.thoughtworks.com/repos/debian buildix main
  • Install the key used to sign the Buildix package repository:
    wget http://buildix.thoughtworks.com/repos/debian/buildix-key.gpg
    apt-key add buildix-key.gpg
  • Update your repository list and install buildix:
    aptitude update
    aptitude install buildix
  • Follow the prompts, and you’re done.

To use it, just point your web browser to your server. Buildix will be installed as the default web site. If you want to use Mingle (and we recommend you give it a go!), you’ll need to accept the license agreement and do some basic configuration. The prompts on the front page will help you configure it. If you don’t want to use Mingle, you need to uninstall it before you can use Buildix.

  • To uninstall Mingle, just run the following command as root:
    aptitude remove mingle

Documentation

The forums can be found here.

Team

The core Buildix team is:

Past members are:

Licence

Buildix is distributed under the Apache 2 Licence.

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

“License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.

“Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.

“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted”
means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as “Not a Contribution.”

“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate
as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of
the Derivative Works; and

(d) If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets “[]”
replaced with your own identifying information. (Don’t include the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the
same “printed page” as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and
limitations under the License.

About

Buildix will quickly and easily provide you with a complete and active Agile Ecosystem.

Continuous Integration, Source Control, Wikis and Bug-Trackers are all cornerstones of a well-run Agile development project. But if you’ve not configured them all before, it can be a bit tricky - and you might miss some of the tight integration that makes them really useful.

At ThoughtWorks, we have considerable experience of configuring Agile development servers in enterprise environments, and we would like to share that knowledge. So we decided to roll our favourite components together - and produced Buildix.

Buildix includes:

  • Subversion for Source Control
  • Mingle for Agile Project Management
  • Cruise Control for Continuous Integration
  • Trac as a wiki and bug-tracker
  • …plus a little bit of our own ThoughtWorks magic, to glue it all together

You can rapidly deploy your new infrastructure: either run Buildix from a LiveCD, or install it on an existing Ubuntu system. Use it as the base of your own software projects. The ‘Add New Project’ wizard will get your team’s projects started quickly and easily.

We find it particularly useful for getting our own project teams up and running really quickly. You can be developing working software in seconds!

Buildix: everything you need to get started in one easy install!