<
From version < 4.1 >
edited by tig
on 2012/05/23 16:16
To version < 3.1 >
edited by tig
on 2012/05/23 16:07
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,7 +14,7 @@
14 14  
15 15  A full KIELER build on the command line is done as follows
16 16  
17 -{{code title="Full Build" linenumbers="true" language="bash"}}
17 +{{code title="Full Build" language="bash" collapse="true"}}
18 18  . /home/java/java-env #sets environment variables for java and maven
19 19  cd build/de.cau.cs.kieler.parent
20 20  mvn clean package
... ... @@ -22,7 +22,7 @@
22 22  
23 23  Afterwards the assembled RCA and P2 repository may be found in {{code language="none"}}build/de.cau.cs.kieler.repository/target{{/code}}. Similarly single plugins or features are found in the {{code language="none"}}target {{/code}}subdirectory of the respective package.
24 24  
25 -= Automatic Builds (Bamboo) =
25 += Automatic Builds =
26 26  
27 27  Maven with Tycho only provides the possibility of headless KIELER builds without starting eclipse. To facilitate automatic builds further Software to monitor source code repositories, start builds after each check-in, notify developers of failed builds, etc. is needed. For KIELER we are using Bamboo by Atlassian
28 28  
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -1998932
1 +1540130
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1998932/Build Management
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1540130/Build Management