<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">


<head>
  <meta http-equiv="content-type" content="text/html;charset=utf-8" />
  <meta http-equiv="Content-Style-Type" content="text/css" />
  <meta name="description" content="geoscience software framework"/>
  <meta name="keywords" content="geophysics"/>
  <title>GeoCraft - Geoscience Software Framework.</title>

  <link rel="stylesheet" href="geocraft.css" type="text/css"/>
</head>


<body>

    <div id="wrap">

    <div id="header">

        <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">
 
            <img class="logo" style="width: 140px; height: 54px;" alt="geocraft logo" src="img/geocraft.gif" />

            <ul id="navlist2">
              <li><a href="index.htm">Home</a></li>
              <li><a href="screenshot.htm">Screen Shots</a></li>
              <li><a href="http://wush.net/trac/geocraft">Development</a></li>
              <li><a href="faq.htm">FAQ</a></li>
              <li id="active"><a href="builds.htm" id="current">Metrics</a></li>
            </ul>
            
            <div class="clear0"></div>
            
        </div></div></div></div></div></div></div></div></div>
        
        <br/>

    </div> <!--header-->

    <br/>

    <div id="content">
        
    <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">
    <h1>Build Metrics Summary</h1>
     <p>
     <ul>
     <li><a href="http://138.32.38.13:8085/browse/GEO-MAIN">Latest Build Results</a></li>
     <li><a href="http://138.32.38.13:8085/download/GEO-MAIN/artifacts/latest/Application-Lint-Report/">Application Lint</a></li>
     <li><a href="http://138.32.38.13:8085/download/GEO-MAIN/artifacts/latest/Unit-Test-Lint-Report/index.html">Tests Lint</a></li>
     <li><a href="http://138.32.38.13:8085/download/GEO-MAIN/artifacts/latest/Checkstyle-Report/index.html">Checkstyle</a></li>
     <li><a href="http://138.32.38.13:8085/download/GEO-MAIN/artifacts/latest/Clover-Report/index.html">Code Coverage</a></li>
     <li><a href="http://138.32.38.13:8085/download/GEO-MAIN/artifacts/latest/JavaDocs/index.html">JavaDoc</a></li>

     </ul>
    </p>
    
   </div></div></div></div></div></div></div></div></div><br/>
   
   
   <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">   
     <h2>Continuous Integration</h2>

      <p>
        If you are not used to developing in a continuous integration environment you may be in for 
        some culture shock. These notes on <a href=http://wush.net/trac/geocraft/wiki/ContinuousIntegration>continuous integration</a>
        may help. 
      </p>

   </div></div></div></div></div></div></div></div></div><br/>

  <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">   
     <h2>Discussion of the metrics</h2>

    <p>
       With a shared code base we have to maintain some kind of commonly agreed upon coding
       standard. We know that having an optimal set of metrics does not equate to having 
       a perfectly designed and debugged architecture but it does let us all trust that the
       code meets some minimal level of quality.
    </p>
    <p>
       If you don't fix up the violations in your code then someone else will 
       probably do it for you. If someone does clean up your code you may then experience
       problems merging your changes back into the svn repository. The simplest way to 
       avoid this is to regularly check that your code is free of the issues that show up
       in these metrics. 
    </p>

  </div></div></div></div></div></div></div></div></div><br/>
  
  <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">   
  <h2>Atlassian Software Tools</h2>
    <p>
       We just moved to using <a href="http://www.atlassian.com/software/clover/">Clover</a> for computing 
       unit test code coverage. This has made the build twice as fast and the reports are much better. 
       Thank you to Atlassian for donating a free license to the GeoCraft project. 
    </p>
    <p>
       We also plan to evaluate using <a href="http://www.atlassian.com/software/crucible/">Crucible</a> and 
       <a href="http://www.atlassian.com/software/bamboo/">Bamboo</a>.
    </p>
  </div></div></div></div></div></div></div></div></div><br/>





  </div> <!--content--> 
    
    
    <div id="side">
    
      
  <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">
  <h3>Lint</h3>
  <p>
  There should be zero compiler warnings for the source code. 
  <p>
  Same for the unit test lint. 
  
  </div></div></div></div></div></div></div></div></div><br/>
        
  <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">
  <h3>Checkstyle</h3>
  <p>
  Ideally, there should be zero checkstyle violations. 
  <p>
  Please remember to include copyright messages on all files. 
  
  </div></div></div></div></div></div></div></div></div><br/>
  
  <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">
  <h3>Unit Tests</h3>
  <p>
  If the tests are broken then the build will be considered broken. 
  <p>
  Don't pile new code into the svn repository while the build is broken. 
  <p>
  Either fix the tests or go beat up the person who broke them. 
  
  </div></div></div></div></div></div></div></div></div><br/>
    
  <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">
  <h3>Code Coverage</h3>
  <p>
  This page lets you see how much of your code is being exercised by running the unit tests. 
  <p>
  When developing code you may prefer to use a plugin to your IDE such as Coverlipse.
  <p>
  
  </div></div></div></div></div></div></div></div></div><br/>

  <div class="t"><div class="b"><div class="l"><div class="r"><div class="bl"><div class="br"><div class="tl"><div class="tr"><div class="spacer">
  <h3>JavaDoc</h3>
  <p>
  If you are like the rest of us you will find that your comments needs editing before 
  they make sense when viewed in the JavaDoc pages. 
  <p>
  JavaDoc errors captures the warnings produced when building the JavaDoc pages. 
  <p>
  There should be no errors. 
  
  </div></div></div></div></div></div></div></div></div><br/>




  </div> <!--side-->

    
    <div class="clear"></div>
    
    <div id="footer">
            Copyright &copy; 2006 - 2007 <a href="http://conocophillips.com/">ConocoPhillips Inc.</a>.
            All Rights Reserved. 
    </div> <!--footer-->

    
    
</div> <!-- wrap --> 

</body>

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
</script>
<script type="text/javascript">
_uacct = "UA-3162588-1";
urchinTracker();
</script>

</html>
