accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bus...@apache.org
Subject svn commit: r1558295 - /accumulo/site/trunk/content/governance/releasing.mdtext
Date Wed, 15 Jan 2014 05:27:48 GMT
Author: busbey
Date: Wed Jan 15 05:27:48 2014
New Revision: 1558295

URL: http://svn.apache.org/r1558295
Log:
ACCUMULO-1797 Updates release guide to include collecting information about testing. clarifies
some test details.

Modified:
    accumulo/site/trunk/content/governance/releasing.mdtext

Modified: accumulo/site/trunk/content/governance/releasing.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/trunk/content/governance/releasing.mdtext?rev=1558295&r1=1558294&r2=1558295&view=diff
==============================================================================
--- accumulo/site/trunk/content/governance/releasing.mdtext (original)
+++ accumulo/site/trunk/content/governance/releasing.mdtext Wed Jan 15 05:27:48 2014
@@ -47,12 +47,30 @@ Note: There will be times where API comp
 
 ## Testing
 
+Testing for an Accumulo release includes a few steps that a developer may take without a
Hadoop cluster and several that require a working cluster.
+
+### Stand alone
+The following steps can be taken without having an underlying cluster. They SHOULD be handled
with each Hadoop profile available for a given release version. To activate an alternative
profile specify e.g. "-Dhadoop.profile=2" for the Hadoop 2 profile on the Maven commandline.
Some older versions of Accumulo referred to Hadoop profiles diferently; see the README that
came with said versions for details on building against different Hadoop versions.
+
   1. All JUnit tests must pass.  This should be a requirement of any patch so it should never
be an issue of the codebase.
-  - All functional tests must complete successfully.
+    - Use "mvn package" to run against the default profile of a particular release
+    - Use "mvn -Dhadoop.profile=2 package" to test against the Hadoop 2 profile on e.g. 1.4
or 1.5
+    - Use "mvn -Dhadoop.profile=1 package" to test against the Hadoop 1 profile on e.g. 1.6
or later
   - Analyze output of static analysis tools like Findbugs and PMD.
-  - Two 24-hour periods of the randomwalk LongClean test with and without agitation need
to be run successfully on a cluster.
-  - Two 24-hour periods of continuous ingest with and without agitation need to be validated
successfully on a cluster.
-  - Two 72-hour periods of continuous ingest with and without agitation on a cluster. No
validation is necessary but the cluster should be checked to ensure it is still functional.
+  - For versions 1.6 and later, all functional tests must pass via the Maven failsafe plugin.
+    - Use "mvn verify" to run against the default profile of a particular release
+    - Use "mvn -Dhadoop.profile=1 verify" to run the functional tests against the Hadoop
1 profile
+
+### Cluster based
+The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce, and ZooKeeper.
The cluster MAY have any number of worker nodes; it can even be a single node in psuedo-distributed
mode. A cluster with multiple tablet servers SHOULD be used so that more of the code base
will be exercised. For the purposes of release testing, you should note the number of nodes
and versions used. See the Releasing section for more details.
+
+  1. For versions prior to 1.6, all functional tests must complete successfully.
+    - See $ACCUMULO_HOME/test/system/auto/README for details on running the functional tests.
+  - Two 24-hour periods of the randomwalk LongClean test with and without agitation need
to be run successfully.
+    - See $ACCUMULO_HOME/test/system/randomwalk/README for details on running the LongClean
module.
+  - Two 24-hour periods of continuous ingest with and without agitation need to be validated
successfully.
+    - See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying
the continous ingest test.
+  - Two 72-hour periods of continuous ingest with and without agitation. No validation is
necessary but the cluster should be checked to ensure it is still functional.
 
 ## Releasing
 
@@ -61,5 +79,6 @@ Note: There will be times where API comp
     - Be fully built, including a tar.gz of the entire project as well as the documentation.
   - PGP Signatures of the tarball must be signed to a separate file and made available in
the public_html folder of the user creating the release on people.apache.org, along with the
tarball and MD5 and SHA512 checksums.
   - A vote must be made on dev@accumulo. Lazy consensus is not sufficient for a release;
at least 3 +1 votes from PMC members are required. All checksums and signatures need to be
verified before any voter can +1 it. Voting shall last 72 hours.
+    - Voters SHOULD include with their vote details on the tests from the testing section
they have successfully run. If given, said details for each test MUST include: the number
of worker nodes in the cluster, the operating system and version, the Hadoop version, and
the Zookeeper version. All such gathered testing information will be included in the release
notes. 
   - Upon successful vote, the new releases can be retagged to remove the RC status and released
on the Accumulo webpage.
   - If at any time the tag needs to be remade due to any sort of error, it should be incremented
to the next release candidate number.
\ No newline at end of file



Mime
View raw message