Imeji Continuous Integration

This page describes how th continuous integration is done fo imeji

imeji POM

• Define the SCM

<scm>
 <url>https://github.com/imeji-community/imeji</url>
 <connection>scm:git:git://github.com/imeji-community/imeji.git</connection>
 <developerConnection>scm:git:git@github.com:imeji-community/imeji.git</developerConnection>
 <tag>develop</tag>
</scm>

• Add a new profile

<profile>
 <id>env-testing-continuum</id>
  <activation>
   <activeByDefault>false</activeByDefault>
  </activation>
  <properties>
   <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
   <jdk.version>1.7</jdk.version>
   <project.build.finalName>imeji</project.build.finalName>
  </properties>
  <build>
  <plugins>
   <plugin>
    <groupId>org.apache.tomcat.maven</groupId>
    <artifactId>tomcat7-maven-plugin</artifactId>
    <version>2.1</version>
    <configuration>
     <url>http://dev-faces.mpdl.mpg.de/manager/text</url>
     <server>tomcat</server>
     <path>/imeji</path>
     <!-- Because we defined the war name in the POM, maven search for the wrong war name. Here we fix it-->
     <warFile>/X/continuum/apache-continuum-1.4.1/data/working-directory/178/target/imeji.war</warFile>
    </configuration>
   </plugin>
  </plugins>
 </build>
</profile>

Continuum

1. Creation of imeji project in the project group:
   1. The POM is directly imported from Git:https://raw.githubusercontent.com/imeji-community/imeji/develop/pom.xml
   2. Following option is used: Checkout multi-module project in single directory
   3. New Goal is added: clean tomcat7:redeploy with arguments --batch-mode --non-recursive

Path Overhead Monitoring

Supply-Chain-Management

Unicode Transformation Format

Apache Continuum

Distributed Revision Control and Source Code Management