Add CI testing for notebooks.

Merge pull request #10 from landlab/mcflugen/test-notebooks

Author: mcflugen

.ci/header.txt

@@ -2,5 +2,4 @@
 .DS_Store
 
 *.out
-*.png
 *.pyc

.ci/notebook_to_script.py

@@ -1,18 +1,43 @@
 env:
   matrix:
   - TRAVIS_PYTHON_VERSION="2.7"
-  - TRAVIS_PYTHON_VERSION="3.4"
   - TRAVIS_PYTHON_VERSION="3.5"
+  - TRAVIS_PYTHON_VERSION="3.6"
+  global:
+    - CONDA_PREFIX=$HOME/miniconda
+    - MINICONDA_URL_BASE="https://repo.continuum.io/miniconda/Miniconda3-latest"
+    - MPLCONFIGDIR=$HOME/.config/matplotlib
 os:
 - linux
 - osx
 sudo: false
+before_install:
+- |
+  if [[ $TRAVIS_OS_NAME == "osx" ]]; then
+    brew remove --force $(brew list)
+    brew cleanup -s
+    rm -rf $(brew --cache)
+  fi
 install:
 - echo "Build on $TRAVIS_OS_NAME for Python $TRAVIS_PYTHON_VERSION"
-- bash .ci/travis/install_python.sh
-- export PATH="$HOME/miniconda/bin:$PATH"
-- conda install -q -c https://conda.anaconda.org/landlab/label/dev landlab
+- |
+  if [[ "$TRAVIS_OS_NAME" == "osx" ]]; then
+    OS="MacOSX-x86_64"
+  else
+    OS="Linux-x86_64"
+  fi
+- curl $MINICONDA_URL_BASE-$OS.sh > $HOME/minconda.sh
+- bash $HOME/minconda.sh -b -p $CONDA_PREFIX
+- export PATH="$CONDA_PREFIX/bin:$PATH"
+- hash -r
+- conda config --set always_yes yes --set changeps1 no
+- conda install python=$TRAVIS_PYTHON_VERSION
+- conda install scripting -c csdms-stack
+- conda install landlab jupyter -c landlab
+- conda info -a && conda list
 script:
-- python .ci/run_tutorials.py
+- mkdir -p $MPLCONFIGDIR
+- "echo backend: Agg > $MPLCONFIGDIR/matplotlibrc"
+- ./run-all-tests.sh
 virtualenv:
   system_site_packages: false

.ci/run_tutorials.py

@@ -0,0 +1,102 @@
+# Contributing to landlab tutorials
+
+Thank you for contributing to the landlab tutorials! We appreciate
+your help as this is largely as volunteer effort! :heart: :heart: :heart:
+
+# How to contribute
+
+## Reporting Bugs
+
+Before creating a bug report, please do at least a cursory check that the
+bug has not already been reported. If it has, add a comment to the existing
+issue instead of opening a new one.
+
+### Submitting a Bug Report
+
+Bugs are tracked as
+[GitHub issues](https://guides.github.com/features/issues/). After you've
+determined you've found a new bug, please open a
+[new issue](https://github.com/landlab/tutorials/issues).
+
+Explain the problem and include additional details to help maintainers
+reproduce the problem. Here are some items that will make it easier
+to track down the source of the problem.
+
+*  **Use a clear and descriptive title** for the issue that identifies the
+   problem.
+*  **Describe the exact steps that reproduce the problem**.
+*  **If possible, provide an example that demonstrates the step** as,
+   for example, a bash script along with input files.
+*  **Describe the behavior you are seeing after these steps**.
+*  **Describe the behavior you expect to see after these steps**.
+
+Additionally, the answers to the following questions about your run
+environment will be helpful.
+
+*  **Which version of landlab are you using?** This could be a specific
+   git sha or a release number.
+*  **What is he name and version of you OS?**
+*  **What compiler are you using?**
+*  **How did you build landlab (if using the development version)?**
+
+
+## Submitting Changes
+
+:tada: Whoa! This is great! We love it when folks contibute code! :tada:
+
+Changes to landlab tutorials should be submitted as 
+[pull requests](http://help.github.com/pull-requests/)).
+
+*  Create a GitHub issue that describes what you propose to do.
+*  Create a topic branch that contains your changes.
+*  Open a new [GitHub pull request](https://github.com/landlab/tutorials/pull/new/master).
+*  Ensure the PR description clearly describes the problem and solution.
+   Include the relevant issue number.
+
+## Styleguides
+
+Use the [PEP8 style guide](https://www.python.org/dev/peps/pep-0008/).
+You may want to use tools like
+[Prospector](http://prospector.landscape.io/en/master/) to help out
+with this.
+
+### Git Commit Messages
+
+* Use the present tense ("Add feature" not "Added feature")
+* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+* Limit the first line to 72 characters or less
+* Reference issues and pull requests liberally
+* Consider starting the commit message with an applicable emoji:
+    * :art: `:art:` when improving the format/structure of the code
+    * :racehorse: `:racehorse:` when improving performance
+    * :non-potable_water: `:non-potable_water:` when plugging memory leaks
+    * :memo: `:memo:` when writing docs
+    * :penguin: `:penguin:` when fixing something on Linux
+    * :apple: `:apple:` when fixing something on macOS
+    * :checkered_flag: `:checkered_flag:` when fixing something on Windows
+    * :bug: `:bug:` when fixing a bug
+    * :fire: `:fire:` when removing code or files
+    * :green_heart: `:green_heart:` when fixing the CI build
+    * :white_check_mark: `:white_check_mark:` when adding tests
+    * :shirt: `:shirt:` when removing linter warnings
+
+## Adding new tutorials
+
+If you would like to create a new tutorial that we have just a few
+conventions that we would like you to follow.
+
+* Create a new folder that will hold your tutorial notebook
+  and data used by your tutorial.
+* Start with the blank tutorial template provided in this repository.
+* Notice that your first cell of code should import `print_function`
+  from `__future__`.  Your tutorial will need to be compatible with
+  both Python 2.7 and 3.4+.
+* If you will be plotting anything, be sure to use include ipython
+  magic command in the first cell to indicate how plots should
+  be rendered.
+* Your tutorial must be able to run without error for the **most
+  recent landlab release**.
+
+Thanks! :heart: :heart: :heart:
+
+The landlab team

.ci/travis/install_python.sh

@@ -1,3 +1,6 @@
+[![Build
+Status](https://travis-ci.org/landlab/tutorials.svg?branch=master)](https://travis-ci.org/landlab/tutorials)
+
 [![Landlab header](./landlab_header.png)](http://landlab.github.io)
 
 Most of these Landlab tutorials can either be read as text files or run as interactive IPython notebooks (recommended!).