qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Qpid > Continuous Integration
Date Sat, 12 Nov 2011 00:44:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2042/9/21/_/styles/combined.css?spaceKey=qpid&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/qpid/Continuous+Integration">Continuous
Integration</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~k-wall">keith
wall</a>
    </h4>
        <br/>
                         <h4>Changes (34)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-changed-lines" >Qpid uses the Apache Infrastructure
CI service, which is a <span class="diff-changed-words"><span class="diff-deleted-chars"style="color:#999;background-color:#fdd;text-decoration:line-through;">-Hudson-</span>[Jenkins|http://jenkins-ci.org/]</span>
installation. More [details|http://wiki.apache.org/general/Hudson] are available from the
Apache wiki. Builds can run on any operating system instance available, or be locked to a
particular type. It may be necessary to restrict some build types to Unix instances only,
but using Hudson will give access to Solaris and Windows Server build environments which will
be useful for interoperability testing. If a build tool such as Maven is used, even tighter
integration with the build process is available, including better test access and the ability
to use the Apache Maven repository for publishing artefacts. <br></td></tr>
            <tr><td class="diff-unchanged" > <br>h2. Implementation <br>
<br></td></tr>
            <tr><td class="diff-changed-lines" >The implementation of CI for Qpid
is being tracked as <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">[QPID-3149|https://issues.apache.org/jira/browse/QPID-3149]
and will be completed during the 0.11 development stream.</span> <span class="diff-added-words"style="background-color:
#dfd;">[QPID-3149|https://issues.apache.org/jira/browse/QPID-3149].</span> <br></td></tr>
            <tr><td class="diff-unchanged" > <br>h2. Operation <br>
<br></td></tr>
            <tr><td class="diff-changed-lines" >All [builds|https://builds.apache.org/hudson/view/M-R/view/Qpid/]
are prefixed with <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">_qpid-_</span>
<span class="diff-added-words"style="background-color: #dfd;">Q{_}pid\-_</span>
to allow grouping together, the _Qpid_ view shows all jobs matching this pattern. <span
class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">The
proposed build entries are as follows:</span> <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
*qpid\-java\-build* - triggered by check-ins to subversion <br>* *qpid\-java\-system\-tests*
- nightly <br>* *qpid\-java\-network\-build* - nightly, from branch with network layer
changes <br>* *qpid\-cpp\-build* - triggered by check-ins to subversion <br>*
*qpid\-cpp\-system\-tests* - nightly <br>* *qpid\-python\-tests* - nightly, full run
of python test kit <br>* *qpid\-java\-_VERSION_\-build* - triggered by check-ins to
subversion, _VERSION_ is current release branch <br>* *qpid\-cpp\-_VERSION_\-build*
- triggered by check-ins to subversion, _VERSION_ is current release branch <br>* *qpid\-java\-release*
- nightly or weekly, full java release with poms <br>* *qpid\-cpp\-release* - nightly
or weekly, full cpp release <br>* *qpid\-interop\-tests* - nightly or weekly <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">The
following builds are configured: <br>|| Build || Trigger || Description || <br>|
[Qpid-Java--Java-TestMatrix|https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-TestMatrix/]
| check-in | Tests the Java client with Java broker. \\ <br>Matrix project permutating
AMQP 0-10/0-9-1 protocols and BDB/In-Memory message store implementations | <br>| [Qpid-Java-Cpp-Test|https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Cpp-Test/]
| check-in | Tests the Java client with the C+\+ Broker. | <br>| [Qpid-Java-Java-Test-Solaris|https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-Solaris/]\\
| every 24h | Tests the Java client with Java broker on Solaris. | <br>| [Qpid-Python-Java-Test|https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/]\\
| every 24h | Tests the Python client with the Java Broker. | <br>| [Qpid-Python-Cpp-Test|https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Cpp-Test/]\\
| every 24h | Tests the Python client with the C+\+ Broker. | <br>| [Qpid-Java-Artefact-Release|https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release/]\\
| every 24h | Generates Maven artefacts for the Java Client/Broker | <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">Note
that it is possible to add builds from branches, to give increased visibility to proposed
changes, and greater confidence in their reliability due to increased testing. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">At
present, these tests run a single profile, such as _default_ or _java.0.10_. As the number
of profiles increases, it may be better to use the Hudson [matrix project|http://wiki.hudson-ci.org/display/HUDSON/Aboutncysa]
feature to paramaterise the system test build around the test profile names. Additionally,
merging of the cpp and java jobs is probably desirable, as is chaining build and test jobs
together. <br></td></tr>
            <tr><td class="diff-unchanged" > <br>A timeout of 60 minutes
is set for all jobs. <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >h4. Java <span class="diff-added-words"style="background-color:
#dfd;">Build</span> Configuration <br></td></tr>
            <tr><td class="diff-unchanged" > <br>The Java builds use the
latest 1.6 release of the JDK, and the latest available Ant version, which are both dependant
on the versions available on the Hudson instance running the job. <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >The release job archives the following
files: <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >* <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">\*\*/release/\*.zip</span>
<span class="diff-added-words"style="background-color: #dfd;">\**/release/*.zip</span>
<br></td></tr>
            <tr><td class="diff-changed-lines" >* <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">\*\*/release/\*.tar.gz</span>
<span class="diff-added-words"style="background-color: #dfd;">\**/release/*.tar.gz</span>
<br></td></tr>
            <tr><td class="diff-changed-lines" >* <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">\*\*/release/maven/\*\*/\*.\*</span>
<span class="diff-added-words"style="background-color: #dfd;">\**/release/maven/**/*.\*</span>
<br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-changed-lines" >h4. Cpp <span class="diff-added-words"style="background-color:
#dfd;">Build</span> Configuration <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">The
following commands each build Qpid: <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">The
following commands are used to perform the Cpp build. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
{{cd trunk/qpid/cpp &amp;&amp; cmake CMakeLists.txt &amp;&amp; make &amp;&amp;
make test}} <br>* {{cd trunk/qpid/cpp &amp;&amp; ./bootstrap &amp;&amp;
./configure &amp;&amp; make &amp;&amp; make test}} <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">{code}
<br>cd trunk/qpid/cpp <br>./bootstrap; ./configure CXXFLAGS=&quot;-Wno-unused-result&quot;;make
clean;&amp;nbsp;make -j4 <br>{code} <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">The
C++ builds cannot use {{cmake}} currently, as it is not installed. The [cmakebuilder Plugin|http://wiki.hudson-ci.org/display/HUDSON/cmakebuilder+Plugin]
also needs to be installed. The autoconf build also fails, due to missing header files: [console
output|^qpid-cpp-build.txt]. Additional tools like {{swig}} also need to be installed, as
well as the packages required for clustering. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">(As
of November 2011, the Ubuntu packages dependencies were: subversion automake autoconf libtool
ruby sasl2-bin uuid-dev g+\+ libicu42 libstdc++6-4.4-dev python-dev python2.6-dev libboost1.40-dev
libboost1.40-dev libboost-program-options-dev libboost-filesystem-dev). <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">Currently
the C++ builds are disabled. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">h4.
{color:#000000}{*}Python Test Configuration{*}{color} <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">h3.
Status <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">The
following commands are used to run the Python tests: <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">The
following builds are currently operational, as of 22 March 2011: <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">{code}
<br>cd trunk/qpid/python <br>ulimit -n 1024 # Workaround QPID-3237 - reduce open
filehandles <br>ant -file qpid-python-test-ant.xml -Dqpid.executable=../java/build/bin/qpid-server
-Dpython.test.ignore=-I../java/test-profiles/python_tests/Java010PythonExcludes &quot;-Dpython.test.modules=-mqpid_tests.broker_0_10
-m qmf.console&quot; -Dqpid.port=25672 -Dqpid.executable.args=&quot;-p 25672 -m 25000&quot;
test <br>{code} <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
[qpid-cpp-build|https://builds.apache.org/hudson/job/qpid-cpp-build/] *disabled* <br>*
[qpid-cpp-0.10-build|https://builds.apache.org/hudson/job/qpid-cpp-0.10-build/] *disabled*
<br>* [qpid-java-build|https://builds.apache.org/hudson/job/qpid-java-build/] <br>*
[qpid-java-0.10-build|https://builds.apache.org/hudson/job/qpid-java-0.10-build/] <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">These
are triggered by subversion check-ins, checked every 15 minutes. <br> <br>* [qpid-java-release|https://builds.apache.org/hudson/job/qpid-java-release/]
<br>* [qpid-java-0.10-release|https://builds.apache.org/hudson/job/qpid-java-0.10-release/]
<br> <br>These are run daily at 00h00. <br> <br>h3. Amazon <br>
<br>Due to the difficulty configuring the ASF Hudson instances to perform a C++ build,
particularly if we intend to use clustering, it will be easier to use an externally hosted
server. [Cloudsoft|http://www.cloudsoftcorp.com/] have generously agreed to provide some Amazon
EC2 instances and storage to run a Hudson CI server. This is currently being tested at the
following URL: <br> <br>* [http://ec2-79-125-76-99.eu-west-1.compute.amazonaws.com:8080/job/qpid-cpp-build/]
<br> <br>This server is an EC2 _c1.medium_ instance, running Ubuntu with an initial
Hudson configuration from [http://www.ciinabox.com/] and has had the following packages installed
via {{apt-get install}}: <br> <br>* build\-essential <br>* autoconf <br>*
libtool <br>* ruby <br>* swig <br>* libboost.\*1.42-dev <br>* uuid\-dev
<br>* libsasl.\*\-dev <br>* sasl2\-bin <br>* cmake <br>* libcorosync\-dev
<br>* libopenais\-dev <br>* ant <br>* .\*jdk.\* <br>* maven2 <br>
<br>* ln /etc/init.d/sonar /usr/bin/sonar <br>* mvn clean install sonar:sonar
<br> <br>It is currently building the C++ code, then the Java code, running all
the Java tests on the _default_ profile, then the system tests only on the _cpp_ profile,
and generating Sonar output for metrics from the release-bin target output. We could also
run some other profiles, and I have configured the build to use an external shared workspace
at {{/home/qpid/workspace}} to simplify this. <br> <br></td></tr>
            <tr><td class="diff-unchanged" >h3. Future <br> <br></td></tr>
            <tr><td class="diff-changed-lines" ><span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">Hudson</span>
<span class="diff-added-words"style="background-color: #dfd;">Jenkins</span> can
be configured to provide many more features with its built-in plugins. These include: <br></td></tr>
            <tr><td class="diff-unchanged" > <br>* FIXME/TODO task reporting
<br>* Javadoc publishing <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">*
Release artifact publishing <br></td></tr>
            <tr><td class="diff-unchanged" >* Coverage reports <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >The use of these plugins will
be investigated once the basic build and test cycle is satisfactorily configured. Future functionality
<span class="diff-changed-words">prop<span class="diff-added-chars"style="background-color:
#dfd;">o</span>sed</span> includes: <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">*
Integrate CPP Tests <br>* Switch CPP Build to use cmake <br>* Integrate Windows
build for Java and CPP Brokers <br></td></tr>
            <tr><td class="diff-unchanged" >* Publishing SNAPSHOT versions of
Maven artefacts to the Apache repository after a successful nightly build <br> <br></td></tr>
            <tr><td class="diff-changed-lines" >h3. <span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">Monitoring</span>
<span class="diff-added-words"style="background-color: #dfd;">Notifications</span>
<br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-deleted-lines" style="color:#999;background-color:#fdd;text-decoration:line-through;">I
propose creation of a new mailing list, _qpid-build@apache.org_ which would receive a copy
of all output from every CI build. Additionally, the results of failing builds should be mailed
to committers that checked in the breaking changes, and a nightly (or weekly) summary from
the release and/or interop test builds should be sent to the _qpid-dev_ list. <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">All
jobs are configured to&amp;nbsp;send email notifications@qpid.apache.org&amp;nbsp;when
a build fails, becomes unstable or returns to stable. <br></td></tr>
            <tr><td class="diff-unchanged" > <br></td></tr>
            <tr><td class="diff-changed-lines" >Currently [Andrew|mailto:grkvlt@apache.org],
<span class="diff-deleted-words"style="color:#999;background-color:#fdd;text-decoration:line-through;">[Rajith|mailto:rajith@apache.org]
and [Robbie|mailto:robbie@apache.org]</span> <span class="diff-added-words"style="background-color:
#dfd;">[Rajith|mailto:rajith@apache.org],&amp;nbsp;[Robbie|mailto:robbie@apache.org]&amp;nbsp;and
[Keith|mailto:kwall@apache.org]</span> have access to the build configurations. <br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <p>Qpid uses the Apache Infrastructure CI service, which is a <a href="http://jenkins-ci.org/"
class="external-link" rel="nofollow">Jenkins</a> installation. More <a href="http://wiki.apache.org/general/Hudson"
class="external-link" rel="nofollow">details</a> are available from the Apache wiki.
Builds can run on any operating system instance available, or be locked to a particular type.
It may be necessary to restrict some build types to Unix instances only, but using Hudson
will give access to Solaris and Windows Server build environments which will be useful for
interoperability testing. If a build tool such as Maven is used, even tighter integration
with the build process is available, including better test access and the ability to use the
Apache Maven repository for publishing artefacts.</p>

<h2><a name="ContinuousIntegration-Implementation"></a>Implementation</h2>

<p>The implementation of CI for Qpid is being tracked as <a href="https://issues.apache.org/jira/browse/QPID-3149"
class="external-link" rel="nofollow">QPID-3149</a>.</p>

<h2><a name="ContinuousIntegration-Operation"></a>Operation</h2>

<p>All <a href="https://builds.apache.org/hudson/view/M-R/view/Qpid/" class="external-link"
rel="nofollow">builds</a> are prefixed with Q<em>pid&#45;</em> to
allow grouping together, the <em>Qpid</em> view shows all jobs matching this pattern.</p>

<p>The following builds are configured:</p>
<div class='table-wrap'>
<table class='confluenceTable'><tbody>
<tr>
<th class='confluenceTh'> Build </th>
<th class='confluenceTh'> Trigger </th>
<th class='confluenceTh'> Description </th>
</tr>
<tr>
<td class='confluenceTd'> <a href="https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-TestMatrix/"
class="external-link" rel="nofollow">Qpid-Java--Java-TestMatrix</a> </td>
<td class='confluenceTd'> check-in </td>
<td class='confluenceTd'> Tests the Java client with Java broker. <br class="atl-forced-newline"
/>
Matrix project permutating AMQP 0-10/0-9-1 protocols and BDB/In-Memory message store implementations
</td>
</tr>
<tr>
<td class='confluenceTd'> <a href="https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Cpp-Test/"
class="external-link" rel="nofollow">Qpid-Java-Cpp-Test</a> </td>
<td class='confluenceTd'> check-in </td>
<td class='confluenceTd'> Tests the Java client with the C+&#43; Broker. </td>
</tr>
<tr>
<td class='confluenceTd'> <a href="https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-Solaris/"
class="external-link" rel="nofollow">Qpid-Java-Java-Test-Solaris</a><br class="atl-forced-newline"
/> </td>
<td class='confluenceTd'> every 24h </td>
<td class='confluenceTd'> Tests the Java client with Java broker on Solaris. </td>
</tr>
<tr>
<td class='confluenceTd'> <a href="https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/"
class="external-link" rel="nofollow">Qpid-Python-Java-Test</a><br class="atl-forced-newline"
/> </td>
<td class='confluenceTd'> every 24h </td>
<td class='confluenceTd'> Tests the Python client with the Java Broker. </td>
</tr>
<tr>
<td class='confluenceTd'> <a href="https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Cpp-Test/"
class="external-link" rel="nofollow">Qpid-Python-Cpp-Test</a><br class="atl-forced-newline"
/> </td>
<td class='confluenceTd'> every 24h </td>
<td class='confluenceTd'> Tests the Python client with the C+&#43; Broker. </td>
</tr>
<tr>
<td class='confluenceTd'> <a href="https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Artefact-Release/"
class="external-link" rel="nofollow">Qpid-Java-Artefact-Release</a><br class="atl-forced-newline"
/> </td>
<td class='confluenceTd'> every 24h </td>
<td class='confluenceTd'> Generates Maven artefacts for the Java Client/Broker </td>
</tr>
</tbody></table>
</div>




<p>A timeout of 60 minutes is set for all jobs.</p>

<h4><a name="ContinuousIntegration-JavaBuildConfiguration"></a>Java Build
Configuration</h4>

<p>The Java builds use the latest 1.6 release of the JDK, and the latest available Ant
version, which are both dependant on the versions available on the Hudson instance running
the job.</p>

<p>Only JUnit test results are reported on currently.</p>

<p>The release job archives the following files:</p>

<ul>
	<li>&#42;<b>/release/</b>.zip</li>
	<li>&#42;<b>/release/</b>.tar.gz</li>
	<li>&#42;<b>/release/maven/</b><b>/</b>.&#42;</li>
</ul>


<h4><a name="ContinuousIntegration-CppBuildConfiguration"></a>Cpp Build
Configuration</h4>

<p>The following commands are used to perform the Cpp build.</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">cd trunk/qpid/cpp
./bootstrap; ./configure CXXFLAGS=<span class="code-quote">"-Wno-unused-result"</span>;make
clean;&amp;nbsp;make -j4
</pre>
</div></div>

<p>(As of November 2011, the Ubuntu packages dependencies were: subversion automake
autoconf libtool ruby sasl2-bin uuid-dev g+&#43; libicu42 libstdc++6-4.4-dev python-dev
python2.6-dev libboost1.40-dev libboost1.40-dev libboost-program-options-dev libboost-filesystem-dev).</p>

<h4><a name="ContinuousIntegration-"></a><font color="#000000"><b>Python
Test Configuration</b></font></h4>

<p>The following commands are used to run the Python tests:</p>

<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent">
<pre class="code-java">cd trunk/qpid/python
ulimit -n 1024 # Workaround QPID-3237 - reduce open filehandles
ant -file qpid-python-test-ant.xml -Dqpid.executable=../java/build/bin/qpid-server -Dpython.test.ignore=-I../java/test-profiles/python_tests/Java010PythonExcludes
<span class="code-quote">"-Dpython.test.modules=-mqpid_tests.broker_0_10 -m qmf.console"</span>
-Dqpid.port=25672 -Dqpid.executable.args=<span class="code-quote">"-p 25672 -m 25000"</span>
test
</pre>
</div></div>


<h3><a name="ContinuousIntegration-Future"></a>Future</h3>

<p>Jenkins can be configured to provide many more features with its built-in plugins.
These include:</p>

<ul>
	<li>FIXME/TODO task reporting</li>
	<li>Javadoc publishing</li>
	<li>Coverage reports</li>
</ul>


<p>The use of these plugins will be investigated once the basic build and test cycle
is satisfactorily configured. Future functionality proposed includes:</p>

<ul>
	<li>Integrate CPP Tests</li>
	<li>Switch CPP Build to use cmake</li>
	<li>Integrate Windows build for Java and CPP Brokers</li>
	<li>Publishing SNAPSHOT versions of Maven artefacts to the Apache repository after
a successful nightly build</li>
</ul>


<h3><a name="ContinuousIntegration-Notifications"></a>Notifications</h3>

<p>All jobs are configured to&nbsp;send email notifications@qpid.apache.org&nbsp;when
a build fails, becomes unstable or returns to stable.</p>

<p>Currently <a href="mailto:grkvlt@apache.org" class="external-link" rel="nofollow">Andrew</a>,
<a href="mailto:rajith@apache.org" class="external-link" rel="nofollow">Rajith</a>,&nbsp;<a
href="mailto:robbie@apache.org" class="external-link" rel="nofollow">Robbie</a>&nbsp;and
<a href="mailto:kwall@apache.org" class="external-link" rel="nofollow">Keith</a>
have access to the build configurations.</p>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/qpid/Continuous+Integration">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=25204999&revisedVersion=25&originalVersion=24">View
Changes</a>
                |
        <a href="https://cwiki.apache.org/confluence/display/qpid/Continuous+Integration?showComments=true&amp;showCommentArea=true#addcomment">Add
Comment</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org


Mime
View raw message