Nuke Travis "build" job

* Building and publishing docs is done on Jenkins now.
* Also, we no longer need to run on Travis's Ubuntu Precise VM, as we updated to Ubuntu Trusty (v14.04.5) libnetcdf binaries some time ago. Looks like we just forgot to update the Travis config when that work was done.

.travis.yml

@@ -9,10 +9,6 @@ language: java
 # Setting sudo to "true" forces the job to run on Travis's standard infrastructure, which seems to fix the problem.
 sudo: true
 
-# Need to run on Ubuntu Precise (v12.04.5) until we rebuild netCDF-C for
-# Ubuntu Trusty (v14.04.5), the new Travis default
-dist: precise
-
 env:
   global:
     # Must specify libnetcdf location this way; the 'jna.library.path' system property does not work.
@@ -26,9 +22,6 @@ env:
     # become part of the S3 URL.
     - TEST_REPORT_DIR="build/reports/allTests"
     - TDS_LOGS_DIR="tds/src/test/content/thredds/logs"
-  matrix:
-    - TASK="build"
-    - TASK="docs"
 
 addons:
   # See the note in travis/after_script.sh about the environment variables that Travis artifact uploading requires.
@@ -42,11 +35,6 @@ addons:
 jdk:
   - oraclejdk8
 
-before_install:
-  - if [[ $TASK == "docs" ]]; then
-      gem install asciidoctor coderay;
-    fi
-
 # Skip the installation step entirely; we don't need it for Gradle builds.
 # https://docs.travis-ci.com/user/customizing-the-build#Skipping-the-Installation-Step
 install: true

travis/after_script.sh

@@ -2,8 +2,6 @@
 
 # Display the S3 URLs of the artifacts that Travis uploaded.
 #
-# Only do so for the "build" task, as that is where the artifacts are actually created.
-#
 # Also, only do so if the ARTIFACTS_KEY variable is set. It--along with ARTIFACTS_SECRET and ARTIFACTS_BUCKET--must be
 # defined in order for Travis to be able to upload artifacts. Because they contain sensitive information, we've defined
 # those values in the Travis repository settings of the Unidata/thredds repo.
@@ -18,7 +16,7 @@
 # An alternative mechanism for protecting sensitive information is encrypted variables. But once again, those
 # variables are not made available to untrusted builds such as pull requests coming from another repository.
 # See https://docs.travis-ci.com/user/environment-variables/#Encrypted-Variables
-if [ $TASK == "build" ] && [ -n "$ARTIFACTS_KEY" ]; then
+if [ -n "$ARTIFACTS_KEY" ]; then
     S3_URL="http://unidata-tds.s3.amazonaws.com/Travis/${TRAVIS_BRANCH}-${TRAVIS_BUILD_NUMBER}/${TRAVIS_JOB_NUMBER}"
     echo "The test report is available at:"
     echo "    $S3_URL/index.html"

travis/script.sh

@@ -1,13 +1,8 @@
 #!/usr/bin/env bash
 
-if [ $TASK == "docs" ]; then
-    echo Building docs
-    # add gradle command for building docs here (once jekyll based doc build system in place)
-else
-  CONTENT_ROOT="-Dtds.content.root.path=$TRAVIS_BUILD_DIR/tds/src/test/content"
-  DOWNLOAD_DIR="-Dtds.download.dir=/tmp/download"
-  UPLOAD_DIR="-Dtds.upload.dir=/tmp/upload"
-  SYSTEM_PROPS="$CONTENT_ROOT $DOWNLOAD_DIR $UPLOAD_DIR"
+CONTENT_ROOT="-Dtds.content.root.path=$TRAVIS_BUILD_DIR/tds/src/test/content"
+DOWNLOAD_DIR="-Dtds.download.dir=/tmp/download"
+UPLOAD_DIR="-Dtds.upload.dir=/tmp/upload"
+SYSTEM_PROPS="$CONTENT_ROOT $DOWNLOAD_DIR $UPLOAD_DIR"
 
-  $TRAVIS_BUILD_DIR/gradlew $SYSTEM_PROPS --info --stacktrace testAll
-fi
+$TRAVIS_BUILD_DIR/gradlew $SYSTEM_PROPS --info --stacktrace testAll