Main Page

From Protege Wiki
Revision as of 10:59, November 11, 2010 by CFaigle (talk) (Contact and further Information)

Jump to: navigation, search

Start Page of Stanford BMIR's Build and Test Automation

Table of Contents

This is the start page on how to (automatically) build and test all applications/projects related to Protégé.

  1. On the overview page you find some background information describing the rationale for caring about automated builds and testing and for establishing a corresponding infrastructure. Here you find also an overview chart displaying the entire infrastructure landscape.
  2. On the tools page there is a short description of all the relevant tools and the rationale for chosing the selected ones.
  3. The administrator guide describes how to install and operate all the servers (currently the http://bmir-hudson1.stanford.edu).
  4. The developer guide is the main page for developers. On these pages developers get answers to questions like
    • How do I initially set up my tools to work with one or more of the Protégé prjects?
    • How do I write test cases?
    • etc.
  5. The QA & project manager guide is the address for everybody interested in the success and quality of builds and code. It gives explanations like
    • What do these metrics tell me?
    • What do I have to do in order to add artifacts (e.g. jar-files) to my repository
  6. The appendices provide additional resources.

Quick links

  1. Overview Chart
  2. Nexus repository: http://bmir-hudson1.stanford.edu/nexus
  3. Hudson Build Sever (build statistics, administration of jobs): http://bmir-hudson1.stanford.edu (only available from "inside")
  4. Sonar Server (code and architecture metrics, coverage report and much more): http://bmir-hudson1.stanford.edu:9000
  5. Tomcat Server (automated UI testing, not of particular interest): http://bmir-hudson1.stanford.edu:8082
  6. SVN-Repository: http://smi-protege.stanford.edu/repos/protege/

Contact and further Information

The selection, installation and testing of the infrastructure as well as the initial transistion from traditional ANT-based to Maven based projects was done by Christian Faigle and Christian Johner. Please contact either for questions related to

  • Selection of tools
  • Administration of tools
  • Converting projects to MAVEN
  • Interpretation and adaptation of reports

This page originally was written by Christian Johner. Mavenprotege.png