Versions Compared

Old Version 22

changes.mady.by.user Brett Porter

Saved on

compared with

New Version 23

changes.mady.by.user Brett Porter

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Installation

Continuum runs at: http://vmbuild.apache.org/continuum

Continuum is installed in /opt/apache-continuum-X.Y.Z, but its configuration is in /home/continuum/services/continuum. It is run using the Java Service Wrapper, and is started by the system init scripts.

Continuum's data is stored in /home/continuum/services/continuum/data:

Subdirectory

Description

build-output-directory

Individual build results for each project

working-directory

Project checkouts. Can be safely deleted if a build is not in progress

continuum

The Continuum build database (Derby)

useres

The Continuum users and security roles (Derby)

Continuum's path is configured in the /etc/init.d/continuum script to include Maven 2.0.9 and Java 6 (which is also used to run Continuum). These will be the defaults used by individual builds - all other Installed Software can be accessed through Continuum profiles and installations in the web interface.

Update the Change History if you make configuration or other changes.

Managing Continuum

Starting/Stopping Continuum

To stop Continuum:

Info

Always run Continuum using these scripts to ensure the proper user and configuration is in place. Do not run Continuum as root!

Code Block
sudo /etc/init.d/continuum stop

To start Continuum:

Code Block
sudo /etc/init.d/continuum start

You can also use sudo /etc/init.d/continuum restart and sudo /etc/init.d/continuum status

Continuum is to be run under the continuum user account only.

System Startup

Continuum is started/stopped via the following links to /etc/init.d/continuum:

  • /etc/rc3.d/S99continuum
  • /etc/rc0.d/K99continuum

Continuum Log Files

You can review these in /home/continuum/services/continuum/logs

Continuum Monitoring

Continuum is monitored by Nagios. See Monitoring.

Continuum Troubleshooting

The Java Service Wrapper should ensure that if Continuum has hung, it gets restarted in a timely manner. If it has been unresponsive for 10 minutes, or if HTTPD has been returning a 503 error for 5 minutes, use the scripts above to restart Continuum.

The restart script may rarely get stuck repeating the following line:

Code Block
Waiting for Apache Continuum to exit...
Waiting for Apache Continuum to exit...
Waiting for Apache Continuum to exit...
...

If this happens more than 5 times, the Wrapper itself has hung. Press Ctrl-C and kill the wrapper by identifying it's PID from /home/continuum/services/continuum/logs/continuum.pid, then run the restart script again.

Maven Settings

The default Maven settings in ~/.m2/settings.xml.

Code Block
xml
xml
<settings>
  <mirrors>
    <mirror>
      <id>archiva</id>
      <url>http://localhost:8081/archiva/repository/releases/</url>
      <mirrorOf>central</mirrorOf>
    </mirror>
  </mirrors>
</settings>

Upgrading Continuum

Currently the steps are:

  • stop continuum
  • move old snapshot out of the way if necessary
  • unpack the new installation into /opt with tar -xzvf /path/to/apache-continuum-X.Y.Z-SNAPSHOT.tar.gz
  • update apps/continuum/WEB-INF/classes/META-INF/plexus/application.xml to set the from-mailbox to continuum@apache.org
  • edit /etc/init.d/continuum to the new installation location
  • start continuum
  • update the Upgrade History page

Ideally, these steps will be better isolated from the installation and/or automated in future.