...

Afterwards the assembled RCA and P2 repository may be found in build/de.cau.cs.kieler.repository/target. Similarly single plugins or features are found in the target subdirectory of the respective package.

...

Continuous

...

At the moment there are four jobs configured for KIELER

Juno 4.2 Continuous Plugins

• Builds and tests KIELER plugins after each commit
• Sends notifications of failed builds to the responsible developer(s)

Juno 4.2 Product Nightly

• Builds all of KIELER including all plugins, features as well as the RCA and the KIELER P2 Repository every night.
• Deploys RCA and repository to the download server
• Assembles the KLay libraries (with and without EMF included) into jar files and deploys them to the download server
• Sends notifications about failed commits to the responsible developer(s) and staff members

Kieler Rating Nightly

• Builds and deploys the KIELER class rating website with a special javadoc doclet

Nightly QA Build

...

and Nightly Builds

There are basically three different build plans for each of the KIELER projects:

1. Continuous Plugins – Compiles the plug-ins and runs the unit tests on them. None of the compiled artifacts are published anywhere. This plan is triggered by pushing stuff into the repositories, giving early feedback regarding whether committed changes break anything.
2. Nightly Product – Compiles the plug-ins and assembles distributable product files and update sites. Distributable files are published in the nightly build directory /home/kieler/public_html/files/nightly. Update sites are published in /home/kieler/public_html/updatesite/nightly. This plan is run once every night.
3. Nightly Rating – Compiles the plug-ins and runs our code quality rating doclet on them. The result is a website published at /home/kieler/public_html/rating. This plan is run once every night.