Difference between revisions of "Main Page"

From Protege Wiki
Jump to: navigation, search
(layout completely changed)
Line 4: Line 4:
 
[[File:infrastructure-2.png|thumb|Infrastructure with all servers and information flow]]
 
[[File:infrastructure-2.png|thumb|Infrastructure with all servers and information flow]]
 
This is the start page on how to (automatically) build and test all applications/projects related to Protégé.
 
This is the start page on how to (automatically) build and test all applications/projects related to Protégé.
# On the <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:OverviewPage|Overview Page]]</span> 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. The page provides a short description of all the relevant tools and the rationale for chosing the selected ones
 
# The <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:AdministratorGuide|Administrator Guide]]</span> describes how to install and operate all the servers (currently the http://bmir-hudson1.stanford.edu).
 
# The <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:DeveloperGuide|Developer Guide]]</span> 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é projects? <strong>New:</strong> Please watch video tutorial.
 
#* How do I write test cases?
 
#* etc.
 
# The <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:QaGuide|QA & Project Manager Guide]]</span> is the address for everybody interested in the success and quality of builds and code. It gives explanations like
 
#* How to write/adjust the pom.xml?
 
#* What do these metrics tell me?
 
#* What do I have to do in order to add artifacts (e.g. jar-files) to my repository
 
  
=Quick links=
+
{| border="1"
# Nexus repository: http://bmir-hudson1.stanford.edu/nexus
+
| On the <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:OverviewPage|Overview Page]]</span>
# Hudson Build Sever (build statistics, administration of jobs): http://bmir-hudson1.stanford.edu  
+
you find
# Sonar Server (code and architecture metrics, coverage report and much more. However best is to start from Hudson server): http://bmir-hudson1.stanford.edu/sonar
+
* some background information describing the rationale for caring about automated builds and testing and for establishing a corresponding infrastructure.
# Tomcat Server (automated UI testing, not of particular interest): http://bmir-hudson1.stanford.edu:8082
+
* an overview chart displaying the entire infrastructure landscape.
# SVN-Repository: http://smi-protege.stanford.edu/repos/protege/
+
* a short description of all the relevant tools and the rationale for chosing the selected ones
 +
 
 +
| The <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:AdministratorGuide|Administrator Guide]]</span>
 +
describes how to install and operate the servers
 +
* Nexus repository: http://bmir-hudson1.stanford.edu/nexus
 +
* Hudson Build Sever (build statistics, administration of jobs): http://bmir-hudson1.stanford.edu  
 +
* Sonar Server (code and architecture metrics, coverage reports and more): http://bmir-hudson1.stanford.edu/sonar (use link from Hudson to Sonar reports instead)
 +
* Tomcat Server (automated UI testing, not of general interest): http://bmir-hudson1.stanford.edu:8080
 +
* SVN-Repository: http://smi-protege.stanford.edu/repos/protege/
 +
 
 +
|-
 +
| The <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:DeveloperGuide|Developer Guide]]</span>
 +
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é projects?
 +
* <strong>New:</strong> Please watch video tutorial.
 +
* How do I write test cases?
 +
* How do I get the lastest downloads?
 +
 
 +
| The <span style="font-variant:small-caps;font-size:1.3em;font-weight:bold">[[Stanford:QaGuide|QA & Project Manager Guide]]</span>
 +
is the address for everybody interested in the success and quality of builds and code. It gives explanations like
 +
* How to write/adjust the pom.xml?
 +
* What do these metrics tell me?
 +
* What do I have to do in order to add artifacts (e.g. jar-files) to my repository
 +
|}
  
 
=Contact and further Information=
 
=Contact and further Information=

Revision as of 13:13, November 18, 2010

Start Page of Stanford BMIR's Build and Test Automation

Guidance Documents

Infrastructure with all servers and information flow

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

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.
  • an overview chart displaying the entire infrastructure landscape.
  • a short description of all the relevant tools and the rationale for chosing the selected ones
The Administrator Guide

describes how to install and operate the servers

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é projects?
  • New: Please watch video tutorial.
  • How do I write test cases?
  • How do I get the lastest downloads?
The QA & Project Manager Guide

is the address for everybody interested in the success and quality of builds and code. It gives explanations like

  • How to write/adjust the pom.xml?
  • What do these metrics tell me?
  • What do I have to do in order to add artifacts (e.g. jar-files) to my repository

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.