Luntbuild : Installation

This is the second part of the little notes about Luntbuild. This gives some basic installation steps of Luntbuild. For an introduction on Luntbuild refer this post.

Using zip distribution (without GUI), in Linux

  1. Download the Luntbuild zip distribution from Luntbuild Sourceforge site, or from Luntbuid Javaforge site. This file is normally named luntbuild-xxx.zip, where xxx denotes the current version.
  1. Extract the zip file into the directory where you want to install Luntbuild, say /opt/luntbuild. Edit the following files with your text editor:
    • Edit file /opt/luntbuild/web/WEB-INF/web.xml:
    • Replace $INSTALL_PATH with your Luntbuild installation path (/opt/luntbuild here).
    • Optinally edit file /opt/luntbuild/web/WEB-INF/users.properties:
    • Replace luntbuild=luntbuild with your desired site administrator password in the format luntbuild=youradminpassword. NOTE, that admin user HAS to be luntbuild
    • If you use LDAP, edit file /opt/luntbuild/web/WEB-INF/ldap.properties and follow Luntbuild documentation to configure LDAP.
  1. If you plan to run Luntbuild in standalone mode (without servlet container), just start Luntbuild as described in standalone section. Else copy all the contents under /opt/luntbuild/web directory, and deploy it as a web application to your application server, or servlet container. For example, if you are using Tomcat servlet container:
    • Make sure Tomcat has been stopped
    • Change to Tomcat install dir: > cd <tomcat install dir>/webapps
    • Make luntbuild directory: > mkdir luntbuild
    • Copy luntbuild/web to webapps: > cp -r /opt/luntbuild/web/* <tomcat install dir>/webapps/luntbuild
    • Start Tomcat

Note: Do not create luntbuild.war file, just copy the contents under /opt/luntbuild/web directory to the luntbuild directory in the appropriate web application directory of your application server, or servlet container.

  1. To launch Luntbuild in standalone mode run the following lines, where ‘localhost’ is the target host and 8080 is the port we need to run the Luntbuild service. (Instead of ‘localhost’ we can also use something like 172.16.7.107)
    cd /opt/luntbuild-1.5.2/
    ./luntbuild-standalone.jar localhost 8080
  1. Now the Luntbuild server is up and running.
  2. But if we need to access the server from outside, we need to open the service port which is 8080, on the host. To open a port in Redhat we can use the command lokkit.
  3. The current installation of Luntbuild server can be accessed via http://localhost:8080/luntbuild/luntbuild-login.html

Using Luntbuild installer (with GUI), in Linux

  1. Make sure you have JDK installed.
  2. Get the ‘luntbuild-xxx-installer.jar’ installer file.
  3. Make it executable by running the following command while you are in the directory it is in.
    chmod +x luntbuild-xxx-installer.jar
  4. Run the installer by running the following line.
    ./luntbuild-xxx-installer.jar
  5. While installing I went on with the default parameters, except the installation path. I selected the install path as ‘/opt/luntbuild-1.5.2/’
  6. To launch Luntbuild in standalone mode run the following lines, where ‘localhost’ is the target host and 8080 is the port we need to run the Luntbuild service. (Instead of ‘localhost’ we can also use something like 172.16.7.107)
    cd /opt/luntbuild-1.5.2/
    ./luntbuild-standalone.jar localhost 8080
  7. Now the Luntbuild server is up and running.
  8. But if we need to access the server from outside, we need to open the service port which is 8080, on the host. To open a port in Redhat we can use the command lokkit.
  9. The current installation of Luntbuild server can be accessed via http://localhost:8080/luntbuild/luntbuild-login.html

Using Luntbuild installer (with GUI), in Windows

  1. Have jdk1.4 or jdk1.5 installed, and add the directory which contains the java and jar executable into your system path
  1. Make sure you get one of Luntbuild supported servlet containers or application servers installed (Servlet2.3 and JSP1.2 support are required), and make sure it has been stopped. Alternatively you can run Luntbuild in standalone mode.
  1. Download Luntbuild installer from Luntbuild Sourceforge site, or from Luntbuid Javaforge site. This file is normally named as luntbuild-xxx-installer.jar, where xxx denotes current version.
  1. Run command java -jar luntbuild-xxx-installer.jar. A GUI will display to guide you through the installation, and Luntbuild will install into the selected directory, let’s say /opt/luntbuild.
  1. Deploy luntbuild.war (located in /opt/luntbuild directory) into your servlet container or application server. Note, that if you selected the deployment directory of your servlet container or application server during installation, the installer will deploy luntbuild.war for you. If you plan to run Luntbuild in standalone mode (without servlet container), just start Luntbuild as described in standalone section.

Access the Luntbuild web application through http://localhost:8080/luntbuild/luntbuild-login.html (Username/Password by default is luntbuild/luntbuild)
For more detailed installation steps, just refer to the original doc.

Luntbuild : Introduction

This is going to be another short series (2-3 posts) about a build automation tool. I got using this during my internship at WaveNET. I don’t this this is going to be a very useful post to many ( I here some one saying when I write useful posts 🙂 ), but it could be at least a reference for some one out there or to me some day.

Introduction

Luntbuild is a powerful build automation and management tool. Continuous Integration or nightly builds can be easily set using a clean web interface. Executed builds are well managed using functions such as search, categorization, promotion, patching, deletion, etc. It also acts as a central build artifacts repository and download area for your whole team.

Why Luntbuild?

You may ask why Luntbuild, while there are already many good build automation tools such as Cruise Control, Anthill, and others. Our answer is:

  • Luntbuild aims at not only being build automation, but also build management system. Executed builds can be categorized, promoted, searched, patched, deleted, etc. This is very important for a nightly builds or Continuous Integration builds, which generate many builds over time.
  • Luntbuild utilizes the project/schedule concept to easily provide build support for parallel development.
  • No configuration files, all jobs are done using web interface. You can set your Luntbuild system in less than thirty minutes.

Luntbuild makes advantage of quite a few open source libraries and frameworks listed here.

Luntbuild homepage http://luntbuild.javaforge.com/

What Luntbuild does?

Basic unit of work in Luntbuild is a build. Build execution is triggered either by a schedule or it can be started manually. A build in Luntbuild performs following steps:

  1. Checks out source code from the Version Control System(s) (VCS).
  2. Labels the current source code based on the current build version.
  3. Runs an Ant/Maven/Command/Rake build script in the source tree.
  4. Runs an Ant/Maven/Command/Rake post build script in the source tree.
  5. Publishes the build log and other build artifacts.

Build configuration, monitoring, and access to the build artifacts are all done using an intuitive web interface. Development and testing teams will have a central area to access the build information.

We shall see basic installation steps in the next post.