continuum-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@apache.org
Subject svn commit: r1600550 [1/6] - in /continuum/site-publish/docs/latest: ./ administrator_guides/ administrator_guides/logging/ administrator_guides/security/ developer_guides/ installation/ user_guides/ user_guides/building_project/ user_guides/managing_b...
Date Thu, 05 Jun 2014 00:35:28 GMT
Author: brett
Date: Thu Jun  5 00:35:26 2014
New Revision: 1600550

URL: http://svn.apache.org/r1600550
Log:
Site checkin for project Continuum :: Documentation

Modified:
    continuum/site-publish/docs/latest/administrator_guides/appearance.html
    continuum/site-publish/docs/latest/administrator_guides/build-agent-groups.html
    continuum/site-publish/docs/latest/administrator_guides/build-agents.html
    continuum/site-publish/docs/latest/administrator_guides/buildEnvironment.html
    continuum/site-publish/docs/latest/administrator_guides/buildQueue.html
    continuum/site-publish/docs/latest/administrator_guides/builddefTemplate.html
    continuum/site-publish/docs/latest/administrator_guides/builder.html
    continuum/site-publish/docs/latest/administrator_guides/chroot.html
    continuum/site-publish/docs/latest/administrator_guides/configuration.html
    continuum/site-publish/docs/latest/administrator_guides/distributed-builds.html
    continuum/site-publish/docs/latest/administrator_guides/external-db.html
    continuum/site-publish/docs/latest/administrator_guides/index.html
    continuum/site-publish/docs/latest/administrator_guides/localRepository.html
    continuum/site-publish/docs/latest/administrator_guides/logging/audit-logs.html
    continuum/site-publish/docs/latest/administrator_guides/logging/continuum-logs.html
    continuum/site-publish/docs/latest/administrator_guides/logging/index.html
    continuum/site-publish/docs/latest/administrator_guides/logging/security-logs.html
    continuum/site-publish/docs/latest/administrator_guides/monitoring.html
    continuum/site-publish/docs/latest/administrator_guides/parallelBuilds.html
    continuum/site-publish/docs/latest/administrator_guides/projectgroup.html
    continuum/site-publish/docs/latest/administrator_guides/purgeConfiguration.html
    continuum/site-publish/docs/latest/administrator_guides/queues.html
    continuum/site-publish/docs/latest/administrator_guides/schedules.html
    continuum/site-publish/docs/latest/administrator_guides/security/customising-security.html
    continuum/site-publish/docs/latest/administrator_guides/security/index.html
    continuum/site-publish/docs/latest/administrator_guides/security/ldap.html
    continuum/site-publish/docs/latest/administrator_guides/shutdown.html
    continuum/site-publish/docs/latest/administrator_guides/webdav.html
    continuum/site-publish/docs/latest/apache-continuum.pdf
    continuum/site-publish/docs/latest/dependencies.html
    continuum/site-publish/docs/latest/dependency-info.html
    continuum/site-publish/docs/latest/dependency-management.html
    continuum/site-publish/docs/latest/developer_guides/building.html
    continuum/site-publish/docs/latest/developer_guides/index.html
    continuum/site-publish/docs/latest/developer_guides/xmlrpc.html
    continuum/site-publish/docs/latest/distribution-management.html
    continuum/site-publish/docs/latest/getting-started.html
    continuum/site-publish/docs/latest/index.html
    continuum/site-publish/docs/latest/installation/build-agent.html
    continuum/site-publish/docs/latest/installation/index.html
    continuum/site-publish/docs/latest/installation/standalone.html
    continuum/site-publish/docs/latest/installation/tomcat.html
    continuum/site-publish/docs/latest/installation/upgrade.html
    continuum/site-publish/docs/latest/integration.html
    continuum/site-publish/docs/latest/issue-tracking.html
    continuum/site-publish/docs/latest/license.html
    continuum/site-publish/docs/latest/mail-lists.html
    continuum/site-publish/docs/latest/plugin-management.html
    continuum/site-publish/docs/latest/plugins.html
    continuum/site-publish/docs/latest/project-info.html
    continuum/site-publish/docs/latest/project-summary.html
    continuum/site-publish/docs/latest/release-notes.html
    continuum/site-publish/docs/latest/source-repository.html
    continuum/site-publish/docs/latest/team-list.html
    continuum/site-publish/docs/latest/user_guides/building_project/build_results.html
    continuum/site-publish/docs/latest/user_guides/building_project/cancelling_build.html
    continuum/site-publish/docs/latest/user_guides/building_project/forced_build.html
    continuum/site-publish/docs/latest/user_guides/building_project/index.html
    continuum/site-publish/docs/latest/user_guides/building_project/schedule_build.html
    continuum/site-publish/docs/latest/user_guides/index.html
    continuum/site-publish/docs/latest/user_guides/managing_builddef/index.html
    continuum/site-publish/docs/latest/user_guides/managing_project/addProject.html
    continuum/site-publish/docs/latest/user_guides/managing_project/editProject.html
    continuum/site-publish/docs/latest/user_guides/managing_project/index.html
    continuum/site-publish/docs/latest/user_guides/managing_project/removeProject.html
    continuum/site-publish/docs/latest/user_guides/managing_project/workingCopy.html
    continuum/site-publish/docs/latest/user_guides/notification/index.html
    continuum/site-publish/docs/latest/user_guides/notification/irc.html
    continuum/site-publish/docs/latest/user_guides/notification/jabber.html
    continuum/site-publish/docs/latest/user_guides/notification/mail.html
    continuum/site-publish/docs/latest/user_guides/notification/msn.html
    continuum/site-publish/docs/latest/user_guides/notification/wagon.html
    continuum/site-publish/docs/latest/user_guides/release/index.html
    continuum/site-publish/docs/latest/user_guides/release/perform.html
    continuum/site-publish/docs/latest/user_guides/release/prepare.html
    continuum/site-publish/docs/latest/user_guides/release/release_results.html
    continuum/site-publish/docs/latest/user_guides/report/index.html
    continuum/site-publish/docs/latest/user_guides/viewing_queues/index.html

Modified: continuum/site-publish/docs/latest/administrator_guides/appearance.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/appearance.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/appearance.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/appearance.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Configure Appearance<a name="Configure_Appearance"></a></h2><!-- %{toc|section=0} --><div class="section"><h3><a name="Banner">Banner</a></h3><p>You can configure the right logo of the banner including title and link on the image. You have to add some information in a POM (like a company POM) (coming from org.apache:apache in this example):</p><div class="source"><pre>  &lt;organization&gt;
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Configure Appearance<a name="Configure_Appearance"></a></h2><!-- %{toc|section=0} -
 -><div class="section"><h3><a name="Banner">Banner</a></h3><p>You can configure the right logo of the banner including title and link on the image. You have to add some information in a POM (like a company POM) (coming from org.apache:apache in this example):</p><div class="source"><pre>  &lt;organization&gt;
     &lt;name&gt;The Apache Software Foundation&lt;/name&gt;
     &lt;url&gt;http://www.apache.org/&lt;/url&gt;
   &lt;/organization&gt;
@@ -404,7 +404,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/build-agent-groups.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/build-agent-groups.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/build-agent-groups.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/build-agent-groups.html Thu Jun  5 00:35:26 2014
@@ -61,7 +61,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -71,7 +71,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -388,7 +388,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Managing Build Agent Groups<a name="Managing_Build_Agent_Groups"></a></h2><p>A Build Agent Group provides a logical association of Build Agents so that it can be attached to a Build Environment providing the user control on which agents it wants the project to be built.</p><p>From the menu, choose the 'Build Agents' item</p><img src="../images/build-agents-menu.png" alt="Build Agents Menu" /><p>You will see a list of the existing Build Agent Groups in the Build Agent Groups Section, if any.</p><img src="../images/build-agent-groups.png" alt="Build Agent Groups List" /><p>To add a new Build Agent Group, click the 'Add' button.</p><p>To edit an existing Build Agent Group, click the 'edit' link to the right of the entry.</p><p>You will be prompted to enter or edit the Build Agent Group Name and its associated Build Agent(s):</p><img src="../images/build-agent-groups-edit.png" alt="Add/Edit Build Agent Group" /><p>Build Agent can be associated to one or 
 more Build Agent Group</p><p>To use a Build Agent Group in a Project, you need to attach it to a build environment.</p><p>Refer to <a href="./buildEnvironment.html">Attach Build Agent Group to a Build Environment</a></p></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Managing Build Agent Groups<a name="Managing_Build_Agent_Groups"></a></h2><p>A Buil
 d Agent Group provides a logical association of Build Agents so that it can be attached to a Build Environment providing the user control on which agents it wants the project to be built.</p><p>From the menu, choose the 'Build Agents' item</p><img src="../images/build-agents-menu.png" alt="Build Agents Menu" /><p>You will see a list of the existing Build Agent Groups in the Build Agent Groups Section, if any.</p><img src="../images/build-agent-groups.png" alt="Build Agent Groups List" /><p>To add a new Build Agent Group, click the 'Add' button.</p><p>To edit an existing Build Agent Group, click the 'edit' link to the right of the entry.</p><p>You will be prompted to enter or edit the Build Agent Group Name and its associated Build Agent(s):</p><img src="../images/build-agent-groups-edit.png" alt="Add/Edit Build Agent Group" /><p>Build Agent can be associated to one or more Build Agent Group</p><p>To use a Build Agent Group in a Project, you need to attach it to a build environment.<
 /p><p>Refer to <a href="./buildEnvironment.html">Attach Build Agent Group to a Build Environment</a></p></div>
       </div>
     </div>
     <div class="clear">
@@ -397,7 +397,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/build-agents.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/build-agents.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/build-agents.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/build-agents.html Thu Jun  5 00:35:26 2014
@@ -61,7 +61,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -71,7 +71,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -388,7 +388,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Managing Build Agents<a name="Managing_Build_Agents"></a></h2><p>Before this, you may want to enable the Distributed Builds option in the <a href="./configuration.html">General Configuration</a> and <a href="../installation/build-agent.html">install a Build Agent</a>, or read about the <a href="./distributed-builds.html">Distributed Builds</a> feature.</p><p>From the menu, choose the <b>Build Agents</b> item</p><img src="../images/build-agents-menu.png" alt="Build Agents Menu" /><p>You will see a list of the existing Build Agents, if any.</p><img src="../images/build-agents.png" alt="Build Agents List" /><p>To add a new Build Agent, click the <b>Add</b> button. You will be prompted to enter the Build Agent URL and Description.</p><p>To edit an existing Build Agent, click the <b>Edit</b> link to the right of the entry. You will be prompted to edit the Build Agent Description.</p><p><b>Note:</b> Once a Build Agent has been saved you can not change its 
 URL.</p><img src="../images/build-agent-edit.png" alt="Add/Edit Build Agent" /><p>Be sure to enable the agent by checking the <b>Enabled</b> checkbox.</p><p>After you save your changes, verify that the <b>Enabled</b> checkbox is checked. If it is not checked, most likely Continuum was unable to ping the agent. Consult the log file for additional information.</p></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Managing Build Agents<a name="Managing_Build_Agents"></a></h2><p>Before this, you m
 ay want to enable the Distributed Builds option in the <a href="./configuration.html">General Configuration</a> and <a href="../installation/build-agent.html">install a Build Agent</a>, or read about the <a href="./distributed-builds.html">Distributed Builds</a> feature.</p><p>From the menu, choose the <b>Build Agents</b> item</p><img src="../images/build-agents-menu.png" alt="Build Agents Menu" /><p>You will see a list of the existing Build Agents, if any.</p><img src="../images/build-agents.png" alt="Build Agents List" /><p>To add a new Build Agent, click the <b>Add</b> button. You will be prompted to enter the Build Agent URL and Description.</p><p>To edit an existing Build Agent, click the <b>Edit</b> link to the right of the entry. You will be prompted to edit the Build Agent Description.</p><p><b>Note:</b> Once a Build Agent has been saved you can not change its URL.</p><img src="../images/build-agent-edit.png" alt="Add/Edit Build Agent" /><p>Be sure to enable the agent by che
 cking the <b>Enabled</b> checkbox.</p><p>After you save your changes, verify that the <b>Enabled</b> checkbox is checked. If it is not checked, most likely Continuum was unable to ping the agent. Consult the log file for additional information.</p></div>
       </div>
     </div>
     <div class="clear">
@@ -397,7 +397,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/buildEnvironment.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/buildEnvironment.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/buildEnvironment.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/buildEnvironment.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <!-- %{toc|section=0} --><div class="section"><h2>Managing Build Environments<a name="Managing_Build_Environments"></a></h2><p>In continuum, Build Environments allow you to create and manage multiple build configurations. Once you have defined the Build Environments you can configure project Build Definitions or <a href="./builddefTemplate.html">Build Definition Templates</a> to use them.</p><p><i>Note: Build Environments affect the versions of specific tools used to execute builds and their environments. They are not intended to replace things like Maven build profiles.</i></p><div class="section"><h3>Build Environments<a name="Build_Environments"></a></h3><p>Build Environments are named groupings of <a href="./builder.html">Installations</a>. By grouping the collection of Tools and Environment Variables, you define a configuration that can be used to build a project. To define a Build Environment, you specify a human friendly name and add one or more Installations. Once de
 fined, the Build Environment is available for use. You can then specify what Build Environment to use in your project's Build Definitions or in your Build Definition Templates. When continuum detects that a project needs to be built, it uses the Tool Installations to construct the paths to the expected executables (ie. Maven build definitions construct paths to the mvn executable and the java executable). Additional Installations are translated into name/value pairs that are passed through to the constructed command's environment.</p><p>As of Continuum 1.2.1, build environments can be used in releasing projects. This is set upon supplying the release prepare parameters during the <a href="../user_guides/release/prepare.html"> Release preparation</a> of the project.</p><div class="section"><h4>Creating a Build Environment<a name="Creating_a_Build_Environment"></a></h4><p>From the menu, choose the 'Build Environments' entry</p><img src="../images/buildenv-menu.png" alt="Build Environm
 ent Menu" /><p>Enter a name</p><img src="../images/buildenv-add.png" alt="Add Build Environment" /></div><div class="section"><h4><a name="Attach_Build_Agent_Group_to_a_Build_Environment">Attach Build Agent Group to a Build Environment</a></h4><p>The list box contains all available Build Agent Groups. The list box will only be visible if Distributed Builds is enabled in the <a href="./configuration.html">General Configuration</a> Page</p><img src="../images/profile-build-agent-group.png" alt="Add Build Agent Group to Build Environment" /></div><div class="section"><h4>Attaching the related Installations<a name="Attaching_the_related_Installations"></a></h4><p>When editing a Build Environment, the Installation list box contains all defined Installations. You can only specify a single Tool Installation per type (jdk, maven, maven2, ant). However, you may specify multiple Environment Variable Installations.</p><img src="../images/buildenv-setup-jdk.png" alt="Adding Installations to Bui
 ld Environment" /></div><div class="section"><h4>Setting a Build Definition's Build Environment<a name="Setting_a_Build_Definitions_Build_Environment"></a></h4><p>The way you configure builds to use your newly created Build Environments is by setting it in either a project Build Definition or in the continuum Build Definition Templates. The following example sets the Build Environment of a specific project's Build Definition. </p><img src="../images/buildenv-in-builddef.png" alt="Setup Build Environment" /></div><div class="section"><h4>Installations used in Notification mail<a name="Installations_used_in_Notification_mail"></a></h4><p>Build notifications send along information about the environment in which the project was built.</p><ul><li>Java Home version : coming from $JAVA_HOME/bin/java -version.</li><li>Builder version : coming from builder used version arg (mvn used -v, ant use -version). </li></ul><div class="source"><pre>  Java Home version : 
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><!-- %{toc|section=0} --><div class="section"><h2>Managing Build Environments<a name="Managing_Build_Environ
 ments"></a></h2><p>In continuum, Build Environments allow you to create and manage multiple build configurations. Once you have defined the Build Environments you can configure project Build Definitions or <a href="./builddefTemplate.html">Build Definition Templates</a> to use them.</p><p><i>Note: Build Environments affect the versions of specific tools used to execute builds and their environments. They are not intended to replace things like Maven build profiles.</i></p><div class="section"><h3>Build Environments<a name="Build_Environments"></a></h3><p>Build Environments are named groupings of <a href="./builder.html">Installations</a>. By grouping the collection of Tools and Environment Variables, you define a configuration that can be used to build a project. To define a Build Environment, you specify a human friendly name and add one or more Installations. Once defined, the Build Environment is available for use. You can then specify what Build Environment to use in your projec
 t's Build Definitions or in your Build Definition Templates. When continuum detects that a project needs to be built, it uses the Tool Installations to construct the paths to the expected executables (ie. Maven build definitions construct paths to the mvn executable and the java executable). Additional Installations are translated into name/value pairs that are passed through to the constructed command's environment.</p><p>As of Continuum 1.2.1, build environments can be used in releasing projects. This is set upon supplying the release prepare parameters during the <a href="../user_guides/release/prepare.html"> Release preparation</a> of the project.</p><div class="section"><h4>Creating a Build Environment<a name="Creating_a_Build_Environment"></a></h4><p>From the menu, choose the 'Build Environments' entry</p><img src="../images/buildenv-menu.png" alt="Build Environment Menu" /><p>Enter a name</p><img src="../images/buildenv-add.png" alt="Add Build Environment" /></div><div class=
 "section"><h4><a name="Attach_Build_Agent_Group_to_a_Build_Environment">Attach Build Agent Group to a Build Environment</a></h4><p>The list box contains all available Build Agent Groups. The list box will only be visible if Distributed Builds is enabled in the <a href="./configuration.html">General Configuration</a> Page</p><img src="../images/profile-build-agent-group.png" alt="Add Build Agent Group to Build Environment" /></div><div class="section"><h4>Attaching the related Installations<a name="Attaching_the_related_Installations"></a></h4><p>When editing a Build Environment, the Installation list box contains all defined Installations. You can only specify a single Tool Installation per type (jdk, maven, maven2, ant). However, you may specify multiple Environment Variable Installations.</p><img src="../images/buildenv-setup-jdk.png" alt="Adding Installations to Build Environment" /></div><div class="section"><h4>Setting a Build Definition's Build Environment<a name="Setting_a_Bu
 ild_Definitions_Build_Environment"></a></h4><p>The way you configure builds to use your newly created Build Environments is by setting it in either a project Build Definition or in the continuum Build Definition Templates. The following example sets the Build Environment of a specific project's Build Definition. </p><img src="../images/buildenv-in-builddef.png" alt="Setup Build Environment" /></div><div class="section"><h4>Installations used in Notification mail<a name="Installations_used_in_Notification_mail"></a></h4><p>Build notifications send along information about the environment in which the project was built.</p><ul><li>Java Home version : coming from $JAVA_HOME/bin/java -version.</li><li>Builder version : coming from builder used version arg (mvn used -v, ant use -version). </li></ul><div class="source"><pre>  Java Home version : 
           java version &quot;1.6.0_11&quot;
           Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
           Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode, sharing)
@@ -406,7 +406,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/buildQueue.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/buildQueue.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/buildQueue.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/buildQueue.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Managing Build Queues<a name="Managing_Build_Queues"></a></h2><div class="section"><h3>Adding a Build Queue<a name="Adding_a_Build_Queue"></a></h3><p>By default, there is already a DEFAULT_BUILD_QUEUE that cannot be deleted configured in Continuum. To add more build queues..</p><p>Click the <b>Build Queue</b> link under the <b>Administration</b> section.</p><img src="../images/buildQueue.png" alt="Build Queue" /><p>You will see all the build queues.</p><img src="../images/listBuildQueue.png" alt="Build Queues list" /><p>Here you can add/delete the build queue. Take note that you would only be allowed to create N number of build queues, where N = the Number of Allowed Builds in Parallel set in the Configuration page.</p><p>Input the name for the build queue and save. </p><img src="../images/addBuildQueue.png" alt="Add Parallel Build Queue" /></div><div class="section"><h3>Deleting a Build Queue<a name="Deleting_a_Build_Queue"></a></h3><p>From the buil
 d queue page, you can delete a build queue by clicking the delete icon</p><img src="../images/delete.gif" alt="Delete icon" /></div></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Managing Build Queues<a name="Managing_Build_Queues"></a></h2><div class="section">
 <h3>Adding a Build Queue<a name="Adding_a_Build_Queue"></a></h3><p>By default, there is already a DEFAULT_BUILD_QUEUE that cannot be deleted configured in Continuum. To add more build queues..</p><p>Click the <b>Build Queue</b> link under the <b>Administration</b> section.</p><img src="../images/buildQueue.png" alt="Build Queue" /><p>You will see all the build queues.</p><img src="../images/listBuildQueue.png" alt="Build Queues list" /><p>Here you can add/delete the build queue. Take note that you would only be allowed to create N number of build queues, where N = the Number of Allowed Builds in Parallel set in the Configuration page.</p><p>Input the name for the build queue and save. </p><img src="../images/addBuildQueue.png" alt="Add Parallel Build Queue" /></div><div class="section"><h3>Deleting a Build Queue<a name="Deleting_a_Build_Queue"></a></h3><p>From the build queue page, you can delete a build queue by clicking the delete icon</p><img src="../images/delete.gif" alt="Delet
 e icon" /></div></div>
       </div>
     </div>
     <div class="clear">
@@ -398,7 +398,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/builddefTemplate.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/builddefTemplate.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/builddefTemplate.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/builddefTemplate.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Build Definition Template<a name="Build_Definition_Template"></a></h2><p>From the menu, choose the 'Build Definition Templates' entry</p><img src="../images/builddefinition-templates.png" alt="Build Definition Templates" /><p>You will see all build definition templates and the build definitions which can be added in templates. In this screen you can add/edit/update/delete a build definition (<b>the Continuum defaults can be deleted</b>)</p><img src="../images/builddefinition-templates-list.png" alt="Build Definition Templates" /><p>In the build definition template edit screen, you can easily one or more build definitions.</p><img src="../images/builddefinition-template-edit.png" alt="Build Definition Template Edit " /></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Build Definition Template<a name="Build_Definition_Template"></a></h2><p>From the m
 enu, choose the 'Build Definition Templates' entry</p><img src="../images/builddefinition-templates.png" alt="Build Definition Templates" /><p>You will see all build definition templates and the build definitions which can be added in templates. In this screen you can add/edit/update/delete a build definition (<b>the Continuum defaults can be deleted</b>)</p><img src="../images/builddefinition-templates-list.png" alt="Build Definition Templates" /><p>In the build definition template edit screen, you can easily one or more build definitions.</p><img src="../images/builddefinition-template-edit.png" alt="Build Definition Template Edit " /></div>
       </div>
     </div>
     <div class="clear">
@@ -398,7 +398,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/builder.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/builder.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/builder.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/builder.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Managing Installations<a name="Managing_Installations"></a></h2><p>Continuum allows you to configure the build tools it uses to build projects by defining <a href="./buildEnvironment.html">Build Environments</a>. Installations allow defining environment settings and are the basic unit of a Build Environment.</p><p>For example, say you need to maintain two build environments. One using JDK 5 and Maven 2.0.9 and another using JDK 6 and Maven 2.1.0-M1. To achieve this, you would need to do the following:</p><ol style="list-style-type: decimal"><li>Create Installations for the versions of Java and Maven.</li><li>Create Installations for any environment variables you want to set such as MAVEN_OPTS and ANT_OPTS.</li><li>Create the desired Build Environments, specifying the combination of Installations to use. </li><li>Assign the Build Environments to your Build Definition Templates or project-specific Build Definitions.</li></ol><div class="section"><h3>In
 stallations<a name="Installations"></a></h3><p>Installations are essentially named environment variables. There are currently two types of Installations: Tools and Environment Variables. </p><div class="section"><h4>Tools<a name="Tools"></a></h4><p>Tools are meant to provide locations to pre-defined tool types. Currently, continuum allows you to define locations for the JDK, Maven 2, Maven 1 and Ant. When you create a tool installation, you specify a human-friendly name, the tool type, and the path to tool. Continuum verifies that the specified tool type resides in that location or fails to create the Installation.</p><div class="section"><h5>Example: Defining a Maven2 Installation<a name="Example:_Defining_a_Maven2_Installation"></a></h5><p>From the menu, choose the 'Installations' entry </p><img src="../images/installations.png" alt="Installations" /><p>Here you must choose the Installation Type you want to add (here a Tool)</p><img src="../images/installation-type-choice.png" alt
 ="Installation Type Choice" /><p>You must configure the tool you want to add</p><img src="../images/installation-tool-edit.png" alt="Tool Setup" /><p>The value 'Value/Path' field must specify the path to the tool:</p><ul><li>For maven2 : it must be similar to your M2_HOME</li><li>For maven1 : it must be similar to your MAVEN_HOME</li><li>For ant : it must be similar to your ANT_HOME</li></ul><p>Continuum validates the path specified depending on the type of Tool:</p><ul><li>For maven2 : &lt;path&gt;/bin/mvn -v will be tested</li><li>For maven1 : &lt;path&gt;/bin/maven -v will be tested</li><li>For ant : &lt;path&gt;/bin/ant -v will be tested</li></ul><p>If the path you specify fails the test, the following error will be displayed:</p><img src="../images/installation-validation-failed.png" alt="Installation validation failed " /><p>You can use the checkbox if you want to create a Build Environment with the same name as your Tool name. </p></div></div><div class="section"><h4>Environm
 ent Variables<a name="Environment_Variables"></a></h4><p>Environment Variables are simply a means to store environment settings using a human-friendly name. Once defined, they can be used to affect the build tools used to build your projects. They consist of a human-friendly name, the name of the environment variable to set and the value. Unlike Tools, Environment Variables are not constrained by continuum. No validation is performed to validate the values. </p><div class="section"><h5>Example: Defining a Java Heap size Environment Variable for Maven2 Tools<a name="Example:_Defining_a_Java_Heap_size_Environment_Variable_for_Maven2_Tools"></a></h5><p>From the menu, choose the 'Installations' entry</p><img src="../images/installations.png" alt="Installations" /><p>Select the Environment Variable Installation type</p><img src="../images/installation-type-choice-envvar.png" alt="Select env var as tool type" /><p>And finally, specify the human-friendly name, the environment variable name
  and the corresponding value. Here we define MAVEN_OPTS that will set the Java heap size to 256 Megabytes.</p><img src="../images/installation-envvar-edit.png" alt="Define the env var name and value" /></div></div></div></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Managing Installations<a name="Managing_Installations"></a></h2><p>Continuum allows
  you to configure the build tools it uses to build projects by defining <a href="./buildEnvironment.html">Build Environments</a>. Installations allow defining environment settings and are the basic unit of a Build Environment.</p><p>For example, say you need to maintain two build environments. One using JDK 5 and Maven 2.0.9 and another using JDK 6 and Maven 2.1.0-M1. To achieve this, you would need to do the following:</p><ol style="list-style-type: decimal"><li>Create Installations for the versions of Java and Maven.</li><li>Create Installations for any environment variables you want to set such as MAVEN_OPTS and ANT_OPTS.</li><li>Create the desired Build Environments, specifying the combination of Installations to use. </li><li>Assign the Build Environments to your Build Definition Templates or project-specific Build Definitions.</li></ol><div class="section"><h3>Installations<a name="Installations"></a></h3><p>Installations are essentially named environment variables. There are 
 currently two types of Installations: Tools and Environment Variables. </p><div class="section"><h4>Tools<a name="Tools"></a></h4><p>Tools are meant to provide locations to pre-defined tool types. Currently, continuum allows you to define locations for the JDK, Maven 2, Maven 1 and Ant. When you create a tool installation, you specify a human-friendly name, the tool type, and the path to tool. Continuum verifies that the specified tool type resides in that location or fails to create the Installation.</p><div class="section"><h5>Example: Defining a Maven2 Installation<a name="Example:_Defining_a_Maven2_Installation"></a></h5><p>From the menu, choose the 'Installations' entry </p><img src="../images/installations.png" alt="Installations" /><p>Here you must choose the Installation Type you want to add (here a Tool)</p><img src="../images/installation-type-choice.png" alt="Installation Type Choice" /><p>You must configure the tool you want to add</p><img src="../images/installation-too
 l-edit.png" alt="Tool Setup" /><p>The value 'Value/Path' field must specify the path to the tool:</p><ul><li>For maven2 : it must be similar to your M2_HOME</li><li>For maven1 : it must be similar to your MAVEN_HOME</li><li>For ant : it must be similar to your ANT_HOME</li></ul><p>Continuum validates the path specified depending on the type of Tool:</p><ul><li>For maven2 : &lt;path&gt;/bin/mvn -v will be tested</li><li>For maven1 : &lt;path&gt;/bin/maven -v will be tested</li><li>For ant : &lt;path&gt;/bin/ant -v will be tested</li></ul><p>If the path you specify fails the test, the following error will be displayed:</p><img src="../images/installation-validation-failed.png" alt="Installation validation failed " /><p>You can use the checkbox if you want to create a Build Environment with the same name as your Tool name. </p></div></div><div class="section"><h4>Environment Variables<a name="Environment_Variables"></a></h4><p>Environment Variables are simply a means to store environme
 nt settings using a human-friendly name. Once defined, they can be used to affect the build tools used to build your projects. They consist of a human-friendly name, the name of the environment variable to set and the value. Unlike Tools, Environment Variables are not constrained by continuum. No validation is performed to validate the values. </p><div class="section"><h5>Example: Defining a Java Heap size Environment Variable for Maven2 Tools<a name="Example:_Defining_a_Java_Heap_size_Environment_Variable_for_Maven2_Tools"></a></h5><p>From the menu, choose the 'Installations' entry</p><img src="../images/installations.png" alt="Installations" /><p>Select the Environment Variable Installation type</p><img src="../images/installation-type-choice-envvar.png" alt="Select env var as tool type" /><p>And finally, specify the human-friendly name, the environment variable name and the corresponding value. Here we define MAVEN_OPTS that will set the Java heap size to 256 Megabytes.</p><img s
 rc="../images/installation-envvar-edit.png" alt="Define the env var name and value" /></div></div></div></div>
       </div>
     </div>
     <div class="clear">
@@ -398,7 +398,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/chroot.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/chroot.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/chroot.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/chroot.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -289,7 +289,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Running builds in chroot jail<a name="Running_builds_in_chroot_jail"></a></h2><p>Feature not yet finished! See <a class="externalLink" href="http://jira.codehaus.org/browse/CONTINUUM-1731">CONTINUUM-1731</a></p><p>You could make continuum run the builds in each project group in a separate chroot jail so they don't interfere with each other for security and stability issues. It requires a fair amount of work to setup the system.</p><p>There are still some security concerns. The user could escape the chroot jail.</p></div><div class="section"><h2>Creating a chroot jail<a name="Creating_a_chroot_jail"></a></h2><p>Installed <a class="externalLink" href="http://olivier.sessink.nl/jailkit/jailkit-2.5.tar.bz2">jailkit</a> ( <a class="externalLink" href="http://olivier.sessink.nl/jailkit/howtos_chroot_shell.html">howto</a> )</p><p>Add chroot to /etc/sudoers and comment out requiretty</p><div class="source"><pre> jetty ALL=NOPASSWD:/usr/sbin/chroot</pre></div
 ><p>Add /usr/sbin to the PATH in /home/jetty/.bash_profile</p></div><div class="section"><h2>Create the jail<a name="Create_the_jail"></a></h2><div class="source"><pre>export JAIL=/home/jail/org.apache.continuum
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Running builds in chroot jail<a name="Running_builds_in_chroot_jail"></a></h2><p>Fe
 ature not yet finished! See <a class="externalLink" href="http://jira.codehaus.org/browse/CONTINUUM-1731">CONTINUUM-1731</a></p><p>You could make continuum run the builds in each project group in a separate chroot jail so they don't interfere with each other for security and stability issues. It requires a fair amount of work to setup the system.</p><p>There are still some security concerns. The user could escape the chroot jail.</p></div><div class="section"><h2>Creating a chroot jail<a name="Creating_a_chroot_jail"></a></h2><p>Installed <a class="externalLink" href="http://olivier.sessink.nl/jailkit/jailkit-2.5.tar.bz2">jailkit</a> ( <a class="externalLink" href="http://olivier.sessink.nl/jailkit/howtos_chroot_shell.html">howto</a> )</p><p>Add chroot to /etc/sudoers and comment out requiretty</p><div class="source"><pre> jetty ALL=NOPASSWD:/usr/sbin/chroot</pre></div><p>Add /usr/sbin to the PATH in /home/jetty/.bash_profile</p></div><div class="section"><h2>Create the jail<a name=
 "Create_the_jail"></a></h2><div class="source"><pre>export JAIL=/home/jail/org.apache.continuum
 jk_init -v -j $JAIL basicshell netbasics
 jk_cp -j $JAIL /bin/uname
 jk_cp -j $JAIL /usr/bin/expr
@@ -342,7 +342,7 @@ export JAVA_HOME=/usr/java/default
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/configuration.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/configuration.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/configuration.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/configuration.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Managing General Configuration<a name="Managing_General_Configuration"></a></h2><p>The first time you start Continuum, you will see the 'General Configuration' page. This page is preconfigured with default values.</p><img src="../images/configuration.png" alt="General Configuration" /><table border="1" class="bodyTable"><tr class="a"><td align="left">Working Directory</td><td align="left">The directory where all projects will be checked out</td></tr><tr class="b"><td align="left">Build Output Directory</td><td align="left">The directory where all build output will be stored</td></tr><tr class="a"><td align="left">Release Output Directory</td><td align="left">The directory where all release output will be stored</td></tr><tr class="b"><td align="left">Deployment Repository Directory</td><td align="left">The directory where generated maven2 artifacts will be stored. This directory will be respect a repository structure. It is independant of the maven d
 eploy phase</td></tr><tr class="a"><td align="left">Base URL</td><td align="left">The base Continuum URL. This URL is used in notifications</td></tr><tr class="b"><td align="left">Number of Allowed Builds in Parallel</td><td align="left">The number of build queues that will be utilized to build projects. This allows concurrent checkouts and builds of multiple projects. Available since version 1.3.1.</td></tr><tr class="a"><td align="left">Enable Distributed Builds</td><td align="left">When checked, this Continuum instance will delegate all builds to configured agents.</td></tr><tr class="b"><td align="left">Shared Secret Password</td><td align="left">The pre-shared key (PSK) between the master and all configured agents. The PSK will need to be copied to all configured agents.</td></tr></table><p>You can modify values or keep defaults then save. </p><p>Although Continuum defaults to storing its data within the installation, it is a best practice to separate the installation and data 
 directories.</p><p>These values can be pre-configured in continuum.xml. Make sure that Continuum is not running when editing this file.</p><p>You can modify values at a later time with the following steps:</p><ol style="list-style-type: decimal"><li>Login to Continuum with an Administrator account</li><li>Click the <b>Configuration</b> link under the <b>Administration</b> section<img src="../images/configuration-menu.png" alt="General Configuration Menu" /></li><li>Click the <b>Edit</b> button</li></ol></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Managing General Configuration<a name="Managing_General_Configuration"></a></h2><p>
 The first time you start Continuum, you will see the 'General Configuration' page. This page is preconfigured with default values.</p><img src="../images/configuration.png" alt="General Configuration" /><table border="1" class="bodyTable"><tr class="a"><td align="left">Working Directory</td><td align="left">The directory where all projects will be checked out</td></tr><tr class="b"><td align="left">Build Output Directory</td><td align="left">The directory where all build output will be stored</td></tr><tr class="a"><td align="left">Release Output Directory</td><td align="left">The directory where all release output will be stored</td></tr><tr class="b"><td align="left">Deployment Repository Directory</td><td align="left">The directory where generated maven2 artifacts will be stored. This directory will be respect a repository structure. It is independant of the maven deploy phase</td></tr><tr class="a"><td align="left">Base URL</td><td align="left">The base Continuum URL. This URL i
 s used in notifications</td></tr><tr class="b"><td align="left">Number of Allowed Builds in Parallel</td><td align="left">The number of build queues that will be utilized to build projects. This allows concurrent checkouts and builds of multiple projects. Available since version 1.3.1.</td></tr><tr class="a"><td align="left">Enable Distributed Builds</td><td align="left">When checked, this Continuum instance will delegate all builds to configured agents.</td></tr><tr class="b"><td align="left">Shared Secret Password</td><td align="left">The pre-shared key (PSK) between the master and all configured agents. The PSK will need to be copied to all configured agents.</td></tr></table><p>You can modify values or keep defaults then save. </p><p>Although Continuum defaults to storing its data within the installation, it is a best practice to separate the installation and data directories.</p><p>These values can be pre-configured in continuum.xml. Make sure that Continuum is not running when
  editing this file.</p><p>You can modify values at a later time with the following steps:</p><ol style="list-style-type: decimal"><li>Login to Continuum with an Administrator account</li><li>Click the <b>Configuration</b> link under the <b>Administration</b> section<img src="../images/configuration-menu.png" alt="General Configuration Menu" /></li><li>Click the <b>Edit</b> button</li></ol></div>
       </div>
     </div>
     <div class="clear">
@@ -398,7 +398,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/distributed-builds.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/distributed-builds.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/distributed-builds.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/distributed-builds.html Thu Jun  5 00:35:26 2014
@@ -61,7 +61,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -71,7 +71,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -388,7 +388,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Understanding Distributed Builds<a name="Understanding_Distributed_Builds"></a></h2><div class="section"><h3>Introduction<a name="Introduction"></a></h3><p>The Distributed Builds is an extension to the base Continuum functionalities that gives us the ability to process multiple independent builds beyond the capacity of a single server's processing power. It also enables us to execute builds on multiple different platforms while retaining a unified view of all project builds.</p></div><div class="section"><h3>Architecture<a name="Architecture"></a></h3><p>Continuum follows a Client-Server model using XML-RPC as the protocol. However, since it uses a bi-directional XML-RPC implementation, we instead distinguish the components by calling them Master and Build Agent.</p><p>The Master is a Continuum instance that has the ability to delegate the builds to registered Build Agents.</p><p>The Build Agent is a standalone Jetty-bundled webapp that listens for a
 ny build requests from the Master it is assigned to.</p><p>There is a one-to-many relationship between the Master and the Build Agents. A Master may have many Build Agents, but each Build Agent can only have one Master.</p><!-- TODO: insert image here --></div><div class="section"><h3>Behavior<a name="Behavior"></a></h3><p>Distributed Builds happen at the project group level of Continuum. When the entire project group is built in the Master, independent projects (single project or multi-module project) are distributed to a single registered Build Agent.</p><p>In a project group containing a mix of projects, the distribution of work goes through the following steps:</p><ol style="list-style-type: decimal"><li>In the Master, a build in the project group is triggered.</li><li>Every independent project within the project group is identified, whether as a single project or a multi-module project. Projects with inter-dependencies cannot be distributed separately, so multi-module projects 
 are delegated to a Build Agent as one build.</li><li>For each independent project, the Master iterates over the list of registered Build Agents and queries each if available. The query is an XML-RPC <tt>ping()</tt> followed by a <tt>getBuildSizeOfAgent()</tt> invocation.</li><li>If there is a Build Agent available, the Master collects the information necessary for the build (SCM URL, project id, etc.) and passes it when invoking <tt>buildProjects()</tt> to the Build Agent with the smallest number of tasks in its queue. The Master also passes the <tt>name</tt> of the local repository of the project's project group. Make sure that a local repository with the same <tt>name</tt> is configured in the Build Agent's configuration file since that is what will be used when the project is built in the build agent. Otherwise, it will use the local repository set in the build agent's <tt>settings.xml</tt> file.</li><li>In the Build Agent, the build request is processed: the build is queued and 
 executed. Upon execution, the Build Agent first performs an SCM checkout or an SCM update followed by an SCM changelog to get the latest update date, then the actual build follows.</li><li>At this point, when the build is running, the Master can invoke <tt>cancelBuild()</tt> which returns a transient build result, and <tt>getBuildResult()</tt> that updates the build output viewed in the Master.</li><li>After the build, the Build Agent returns the complete build result to the Master by invoking the callback method <tt>returnBuildResult()</tt>, which the Master aggregates to provide a unified view of projects.<p>A <tt>ping()</tt> is always called before each XML-RPC invocation to check if the agent is available. If it's not, the agent will be disabled.</p></li></ol><!-- TODO: insert sequence diagram here --></div><div class="section"><h3>Setup<a name="Setup"></a></h3><ul><li><a href="./configuration.html">Enable</a> the Distributed Builds option and set the Shared Secret Password in t
 he General Configuration.</li><li><a href="../installation/build-agent.html">Install and Configure</a> one or more Build Agents.</li><li><a href="./build-agents.html">Add</a> your Build Agents to the Continuum Master.</li><li><a href="./build-agent-groups.html">Add</a> your Build Agents to a Build Agent Group.</li><li><a href="./buildEnvironment.html"> Add</a> your Build Agent Group to a Build Environment.</li><li>Configure a project to use that Build Environment.</li><li>Make sure that the <a href="./localRepository.html"> local repository</a> of the <a href="./projectgroup.html"> project group</a> is properly configured. In this case, it should point to the path of the repository where the Build Agent is installed/running.</li></ul><p><b>Warning:</b> You need to have a central remote repository to store the artifacts created from the Build Agent so that other agents will be able to use the new artifacts.</p></div><div class="section"><h3>Limitations<a name="Limitations"></a></h3><
 ul><li>Only system administrator can enable/disable distributed builds</li><li>Credentials (i.e. svn credentials) are passed along if specified, but if server cache is used it will need to be done individually on the Build Agents</li><li>There is no tracking of SCM changes</li><li>The Build Agent needs a configuration web interface</li><li>All projects in a project group will be distributed to the same Build Agent</li></ul></div><div class="section"><h3>Future Enhancements<a name="Future_Enhancements"></a></h3><ul><li>Remote builders<ul><li>Builders can be installed on remote machines, a Continuum manager will send actions to run to builders. An action can be something to run on all builders, on some of them or eventually only to an available builder if we don't want to run more than one build. Actions can be sent with JMS and builders can apply some filters if they don't want to receive all actions. With that, we can do some parallel builds but the dependency tree must be respected
  for the build order. To work correctly with dependencies, each builder must use a central local repository. Maybe we can use an internal Archiva.</li><li>With Continuum builders configured to receive all commands, users can run multi-platform build for each build definition execution.</li><li>With Continuum builders configured to receive only some project types, users can use a different builder by project group. In this case, the build of all projects will be done quickly because commands are balanced on several servers.</li><li>With Continuum builders configured to build something when it is available, users can install builders on several machine to balance the charge. In this case, it will be possible to run some parallel builds.</li><li>When the builders work is done, a message will be sent to the manager to notify the end of the process.</li><li>With JMS used for the communication, we can add some listeners to create reports/statistics, log some information.</li></ul></li><li
 >Policy-based distribution<ul><li>Next available</li><li>Load balanced</li><li>Targeted environment matching</li></ul></li></ul></div></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Understanding Distributed Builds<a name="Understanding_Distributed_Builds"></a></h2
 ><div class="section"><h3>Introduction<a name="Introduction"></a></h3><p>The Distributed Builds is an extension to the base Continuum functionalities that gives us the ability to process multiple independent builds beyond the capacity of a single server's processing power. It also enables us to execute builds on multiple different platforms while retaining a unified view of all project builds.</p></div><div class="section"><h3>Architecture<a name="Architecture"></a></h3><p>Continuum follows a Client-Server model using XML-RPC as the protocol. However, since it uses a bi-directional XML-RPC implementation, we instead distinguish the components by calling them Master and Build Agent.</p><p>The Master is a Continuum instance that has the ability to delegate the builds to registered Build Agents.</p><p>The Build Agent is a standalone Jetty-bundled webapp that listens for any build requests from the Master it is assigned to.</p><p>There is a one-to-many relationship between the Master an
 d the Build Agents. A Master may have many Build Agents, but each Build Agent can only have one Master.</p><!-- TODO: insert image here --></div><div class="section"><h3>Behavior<a name="Behavior"></a></h3><p>Distributed Builds happen at the project group level of Continuum. When the entire project group is built in the Master, independent projects (single project or multi-module project) are distributed to a single registered Build Agent.</p><p>In a project group containing a mix of projects, the distribution of work goes through the following steps:</p><ol style="list-style-type: decimal"><li>In the Master, a build in the project group is triggered.</li><li>Every independent project within the project group is identified, whether as a single project or a multi-module project. Projects with inter-dependencies cannot be distributed separately, so multi-module projects are delegated to a Build Agent as one build.</li><li>For each independent project, the Master iterates over the list
  of registered Build Agents and queries each if available. The query is an XML-RPC <tt>ping()</tt> followed by a <tt>getBuildSizeOfAgent()</tt> invocation.</li><li>If there is a Build Agent available, the Master collects the information necessary for the build (SCM URL, project id, etc.) and passes it when invoking <tt>buildProjects()</tt> to the Build Agent with the smallest number of tasks in its queue. The Master also passes the <tt>name</tt> of the local repository of the project's project group. Make sure that a local repository with the same <tt>name</tt> is configured in the Build Agent's configuration file since that is what will be used when the project is built in the build agent. Otherwise, it will use the local repository set in the build agent's <tt>settings.xml</tt> file.</li><li>In the Build Agent, the build request is processed: the build is queued and executed. Upon execution, the Build Agent first performs an SCM checkout or an SCM update followed by an SCM changel
 og to get the latest update date, then the actual build follows.</li><li>At this point, when the build is running, the Master can invoke <tt>cancelBuild()</tt> which returns a transient build result, and <tt>getBuildResult()</tt> that updates the build output viewed in the Master.</li><li>After the build, the Build Agent returns the complete build result to the Master by invoking the callback method <tt>returnBuildResult()</tt>, which the Master aggregates to provide a unified view of projects.<p>A <tt>ping()</tt> is always called before each XML-RPC invocation to check if the agent is available. If it's not, the agent will be disabled.</p></li></ol><!-- TODO: insert sequence diagram here --></div><div class="section"><h3>Setup<a name="Setup"></a></h3><ul><li><a href="./configuration.html">Enable</a> the Distributed Builds option and set the Shared Secret Password in the General Configuration.</li><li><a href="../installation/build-agent.html">Install and Configure</a> one or more B
 uild Agents.</li><li><a href="./build-agents.html">Add</a> your Build Agents to the Continuum Master.</li><li><a href="./build-agent-groups.html">Add</a> your Build Agents to a Build Agent Group.</li><li><a href="./buildEnvironment.html"> Add</a> your Build Agent Group to a Build Environment.</li><li>Configure a project to use that Build Environment.</li><li>Make sure that the <a href="./localRepository.html"> local repository</a> of the <a href="./projectgroup.html"> project group</a> is properly configured. In this case, it should point to the path of the repository where the Build Agent is installed/running.</li></ul><p><b>Warning:</b> You need to have a central remote repository to store the artifacts created from the Build Agent so that other agents will be able to use the new artifacts.</p></div><div class="section"><h3>Limitations<a name="Limitations"></a></h3><ul><li>Only system administrator can enable/disable distributed builds</li><li>Credentials (i.e. svn credentials) ar
 e passed along if specified, but if server cache is used it will need to be done individually on the Build Agents</li><li>There is no tracking of SCM changes</li><li>The Build Agent needs a configuration web interface</li><li>All projects in a project group will be distributed to the same Build Agent</li></ul></div><div class="section"><h3>Future Enhancements<a name="Future_Enhancements"></a></h3><ul><li>Remote builders<ul><li>Builders can be installed on remote machines, a Continuum manager will send actions to run to builders. An action can be something to run on all builders, on some of them or eventually only to an available builder if we don't want to run more than one build. Actions can be sent with JMS and builders can apply some filters if they don't want to receive all actions. With that, we can do some parallel builds but the dependency tree must be respected for the build order. To work correctly with dependencies, each builder must use a central local repository. Maybe w
 e can use an internal Archiva.</li><li>With Continuum builders configured to receive all commands, users can run multi-platform build for each build definition execution.</li><li>With Continuum builders configured to receive only some project types, users can use a different builder by project group. In this case, the build of all projects will be done quickly because commands are balanced on several servers.</li><li>With Continuum builders configured to build something when it is available, users can install builders on several machine to balance the charge. In this case, it will be possible to run some parallel builds.</li><li>When the builders work is done, a message will be sent to the manager to notify the end of the process.</li><li>With JMS used for the communication, we can add some listeners to create reports/statistics, log some information.</li></ul></li><li>Policy-based distribution<ul><li>Next available</li><li>Load balanced</li><li>Targeted environment matching</li></u
 l></li></ul></div></div>
       </div>
     </div>
     <div class="clear">
@@ -397,7 +397,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/external-db.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/external-db.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/external-db.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/external-db.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>How to use an external database?<a name="How_to_use_an_external_database"></a></h2><div class="section"><h3>Supported databases<a name="Supported_databases"></a></h3><ul><li>Derby</li><li>MySQL</li><li>Postgres</li><li>MS SQL Server (with modifications)</li><li>Oracle (with modifications)</li></ul></div><div class="section"><h3>Configure Continuum<a name="Configure_Continuum"></a></h3><p>There is some information in the installation guides for the <a href="../installation/standalone.html"> standalone Continuum installation</a> and the <a href="../installation/tomcat.html"> Continuum web application deployed to Tomcat</a>.</p><div class="section"><h4>Standalone version<a name="Standalone_version"></a></h4><p>To use an external database with Continuum standalone, you must configure DataSources in <tt>$CONTINUUM_HOME/contexts/continuum.xml</tt></p><div class="source"><pre>  &lt;!-- continuum database --&gt;
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>How to use an external database?<a name="How_to_use_an_external_database"></a></h2>
 <div class="section"><h3>Supported databases<a name="Supported_databases"></a></h3><ul><li>Derby</li><li>MySQL</li><li>Postgres</li><li>MS SQL Server (with modifications)</li><li>Oracle (with modifications)</li></ul></div><div class="section"><h3>Configure Continuum<a name="Configure_Continuum"></a></h3><p>There is some information in the installation guides for the <a href="../installation/standalone.html"> standalone Continuum installation</a> and the <a href="../installation/tomcat.html"> Continuum web application deployed to Tomcat</a>.</p><div class="section"><h4>Standalone version<a name="Standalone_version"></a></h4><p>To use an external database with Continuum standalone, you must configure DataSources in <tt>$CONTINUUM_HOME/contexts/continuum.xml</tt></p><div class="source"><pre>  &lt;!-- continuum database --&gt;
 
   &lt;New id=&quot;continuum&quot; class=&quot;org.eclipse.jetty.plus.jndi.Resource&quot;&gt;
     &lt;Arg&gt;&lt;Ref id=&quot;wac&quot;/&gt;&lt;/Arg&gt;
@@ -448,7 +448,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 

Modified: continuum/site-publish/docs/latest/administrator_guides/index.html
URL: http://svn.apache.org/viewvc/continuum/site-publish/docs/latest/administrator_guides/index.html?rev=1600550&r1=1600549&r2=1600550&view=diff
==============================================================================
--- continuum/site-publish/docs/latest/administrator_guides/index.html (original)
+++ continuum/site-publish/docs/latest/administrator_guides/index.html Thu Jun  5 00:35:26 2014
@@ -62,7 +62,7 @@ pageTracker._trackPageview();</script>
                 <a href="../../../">Continuum</a>
                 &gt;
       
-                <a href="../">1.4.1</a>
+                <a href="../">1.4.2</a>
                   </div>
             <div class="xright">      
   
@@ -72,7 +72,7 @@ pageTracker._trackPageview();</script>
   
   
     
-             Last Published: 02 Jan 2013
+             Last Published: 05 Jun 2014
             </div>
       <div class="clear">
         <hr/>
@@ -389,7 +389,7 @@ pageTracker._trackPageview();</script>
     </div>
     <div id="bodyColumn">
       <div id="contentBox">
-        <div class="section"><h2>Administrator's Guides<a name="Administrators_Guides"></a></h2><ul><li><a href="./security/index.html">Managing Users and Security</a></li><li><a href="./projectgroup.html">Managing Project Groups</a></li><li><a href="./builder.html">Managing Installations</a></li><li><a href="./buildEnvironment.html">Managing Build Environments</a></li><li><a href="./build-agents.html">Managing Build Agents</a></li><li><a href="./build-agent-groups.html">Managing Build Agent Groups</a></li><li><a href="./schedules.html">Managing Schedules</a></li><li><a href="./configuration.html">Managing General Configuration</a></li><li><a href="./localRepository.html">Managing Local Repositories</a></li><li><a href="./purgeConfiguration.html">Managing Purge Configuration</a></li><li><a href="./parallelBuilds.html">Managing Parallel Builds</a></li><li><a href="./buildQueue.html">Managing Build Queues</a></li><li><a href="./queues.html">Managing Project Queues</a></li><li><a href=
 "./external-db.html">External Databases</a></li><li><a href="./monitoring.html">Monitoring Continuum</a></li><li><a href="./logging/index.html"> Log Files</a></li><li><a href="./appearance.html">Appearance Configuration</a></li><li><a href="./builddefTemplate.html">Build Definition Templates</a></li><li><a href="./shutdown.html">Shutting Down Continuum</a></li><li><a href="./distributed-builds.html">Understanding Distributed Builds</a></li><li><a href="./webdav.html"> Accessing remote working copies using WebDAV</a></li></ul></div>
+        <!-- Licensed to the Apache Software Foundation (ASF) under one --><!-- or more contributor license agreements.  See the NOTICE file --><!-- distributed with this work for additional information --><!-- regarding copyright ownership.  The ASF licenses this file --><!-- to you under the Apache License, Version 2.0 (the --><!-- "License"); you may not use this file except in compliance --><!-- with the License.  You may obtain a copy of the License at --><!--  --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--  --><!-- Unless required by applicable law or agreed to in writing, --><!-- software distributed under the License is distributed on an --><!-- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or implied.  See the License for the --><!-- specific language governing permissions and limitations --><!-- under the License. --><div class="section"><h2>Administrator's Guides<a name="Administrators_Guides"></a></h2><ul><li><a href="./s
 ecurity/index.html">Managing Users and Security</a></li><li><a href="./projectgroup.html">Managing Project Groups</a></li><li><a href="./builder.html">Managing Installations</a></li><li><a href="./buildEnvironment.html">Managing Build Environments</a></li><li><a href="./build-agents.html">Managing Build Agents</a></li><li><a href="./build-agent-groups.html">Managing Build Agent Groups</a></li><li><a href="./schedules.html">Managing Schedules</a></li><li><a href="./configuration.html">Managing General Configuration</a></li><li><a href="./localRepository.html">Managing Local Repositories</a></li><li><a href="./purgeConfiguration.html">Managing Purge Configuration</a></li><li><a href="./parallelBuilds.html">Managing Parallel Builds</a></li><li><a href="./buildQueue.html">Managing Build Queues</a></li><li><a href="./queues.html">Managing Project Queues</a></li><li><a href="./external-db.html">External Databases</a></li><li><a href="./monitoring.html">Monitoring Continuum</a></li><li><a 
 href="./logging/index.html"> Log Files</a></li><li><a href="./appearance.html">Appearance Configuration</a></li><li><a href="./builddefTemplate.html">Build Definition Templates</a></li><li><a href="./shutdown.html">Shutting Down Continuum</a></li><li><a href="./distributed-builds.html">Understanding Distributed Builds</a></li><li><a href="./webdav.html"> Accessing remote working copies using WebDAV</a></li></ul></div>
       </div>
     </div>
     <div class="clear">
@@ -398,7 +398,7 @@ pageTracker._trackPageview();</script>
     <div id="footer">
       <div class="xright" style="text-align: right">
         &#169;  
-          2003-2013
+          2003-2014
     
                   <a href="http://www.apache.org/">The Apache Software Foundation</a>
                 



Mime
View raw message