message: Filled in summary content about how we use Bamboo.
diff: @@ -19,30 +19,72 @@ Continuous Integration
  tool suite. The Axom project uses two Bamboo projects, one on the LC
  Collaboration Zone (CZ) and one on the LC Restricted Zone (RZ).
  -.. important:: Section under construction....
  +The basic mechanics for managing test plans described in
  +:ref:`bambooplan-label` is the same for both Bamboo instances.
  ===========================
  CZ Bamboo Project
  ===========================
  -Describe how we use our CZ Bamboo project ....
  -
  -`Bamboo project <https://lc.llnl.gov/bamboo/browse/ASC>`_
  +We use the `Axom CZ Bamboo project <https://lc.llnl.gov/bamboo/browse/ASC>`_
  +primarily for manually running Bamboo plans on specific branches. For example,
  +if you are working on a branch and you want to build the branch code and run
  +tests on several LC platforms on the CZ with a variety of compilers, you can
  +do this easily. The test plans for for such branch testing are configured so
  +that when a new Axom git branch is created and pushed to our Bitbucket project,
  +the branch will appear in the list of branches on which a plan can be run.
  +
  +There are Bamboo plan options for this branch testing. One is a "smoke test"
  +that will build and run tests on a single platform with our default GNU
  +compiler. The other is a more comprehensive plan that will build and run tests
  +on each of the platform types (e.g., TOSS 2, TOSS 3, BG/Q, Blue OS) with a
  +variety of compilers that we need to support.
  +
  +To run a plan on a specific branch, do the following:
  +
  + #. Log into the CZ Bamboo tool.
  + #. Click on the 'Axom' project.
  + #. Select the test plan you want to run.
  + #. Click on the branch you want to build and test.
  + #. Click the run button on the upper right.
  +
  +Depending on resource availability and what the plan does, the plan may
  +take a while to run. When the plan completes, you will receive an email
  +indicating this and whether everything passed or if there were any failures.
  +If you need to look at the detailed results (e.g., if a test failed), you
  +can do the following:
  +
  + #. Clicking on the branch name in the plan.
  + #. Click on the run number in the summary.
  + #. Click on the 'artifacts' tab.
  + #. Click on the artifact that you want to see. The test plan artifacts
  + contain the detailed output generated by Google Test and FRUIT.
  +
  +We also have one plan that builds and runs tests on the master branch on
  +a selct set of platforms and compilers once per week. Each member of the team
  +receives an email indicating passes and failures of builds and tests.
  ===========================
  RZ Bamboo Project
  ===========================
  -Describe how we use our RZ Bamboo project ....
  +We use the `Axom RZ Bamboo project <https://rzlc.llnl.gov/bamboo/browse/ASC>`_
  +for the bulk of Axom automated build and test operations. This includes:
  +nightly builds and tests of the develop branch on each of the platform types
  +(e.g., TOSS 2, TOSS 3, BG/Q, Blue OS) with a variety of compilers that we need
  +to support, user documentation build and install on LC web pages, and
  +weekly third-party library builds.
  -`Bamboo project <https://rzlc.llnl.gov/bamboo/browse/ASC>`_
  +.. _bambooplan-label:
  -===========================
  -Basic Bamboo Tasks
  -===========================
  +====================================
  +Basic Bamboo Test Plan Management
  +====================================
  +
  +.. important:: Section under construction....
  .. important:: The content below is mainly usage notes. Much of what we want
  to include here will be pulled from `Our Confluence Notes on Bamboo <https://lc.llnl.gov/confluence/display/ASCT/Bamboo+How-To%27s>`_
  