Difference between revisions of "Main Page"
From Protege Wiki
| Line 1: | Line 1: | ||
| − | |||
| − | |||
=Start Page of Stanford BMIR's Build and Test Automation= | =Start Page of Stanford BMIR's Build and Test Automation= | ||
| − | + | =Guidance Documents (table of contents)= | |
[[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é. | ||
| Line 16: | Line 14: | ||
#* What do I have to do in order to add artifacts (e.g. jar-files) to my repository | #* What do I have to do in order to add artifacts (e.g. jar-files) to my repository | ||
| − | + | =Quick links= | |
# Nexus repository: http://bmir-hudson1.stanford.edu/nexus | # Nexus repository: http://bmir-hudson1.stanford.edu/nexus | ||
# Hudson Build Sever (build statistics, administration of jobs): http://bmir-hudson1.stanford.edu | # Hudson Build Sever (build statistics, administration of jobs): http://bmir-hudson1.stanford.edu | ||
| Line 23: | Line 21: | ||
# SVN-Repository: http://smi-protege.stanford.edu/repos/protege/ | # 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 [mailto://c.faigle@gmx.net Christian Faigle] and [mailto://mail@johner.org Christian Johner]. Please contact either for questions related to | 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 [mailto://c.faigle@gmx.net Christian Faigle] and [mailto://mail@johner.org Christian Johner]. Please contact either for questions related to | ||
* Selection of tools | * Selection of tools | ||
Revision as of 12:22, November 18, 2010
Contents
Start Page of Stanford BMIR's Build and Test Automation
Guidance Documents (table of contents)
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. 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 Administrator Guide describes how to install and operate all the servers (currently the http://bmir-hudson1.stanford.edu).
- 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?
- etc.
- 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
Quick links
- 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 report and much more. However best is to start from Hudson server): http://bmir-hudson1.stanford.edu/sonar
- Tomcat Server (automated UI testing, not of particular interest): http://bmir-hudson1.stanford.edu:8082
- 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.
