build: remove dashboard (#14023)

* Since we going to move from Travis to CircleCI we don't want to use the dashboard anymore. Since nobody has been
looking at the dashboard frequently, it just makes things more complicated and additionally we will be using
the Github robot in order to keep track of size changes.

scripts/ci/sources/mode.sh

@@ -13,10 +13,6 @@ is_aot() {
   [[ "${MODE}" = aot ]]
 }
 
-is_payload() {
-  [[ "${MODE}" = payload ]]
-}
-
 is_unit() {
   [[ "${MODE}" =~ ^.*_(optional|required)$ ]]
 }

scripts/ci/travis-deploy.sh

@@ -19,9 +19,7 @@ echo ""
 echo "Starting the deployment script. Running mode: ${DEPLOY_MODE}"
 echo ""
 
-if [[ "${DEPLOY_MODE}" == "dashboard" ]]; then
-  retryCall ${DEPLOY_RETRIES} ./scripts/deploy/deploy-dashboard.sh
-elif [[ "${DEPLOY_MODE}" == "build-artifacts" ]]; then
+if [[ "${DEPLOY_MODE}" == "build-artifacts" ]]; then
   retryCall ${DEPLOY_RETRIES} ./scripts/deploy/publish-build-artifacts.sh
 elif [[ "${DEPLOY_MODE}" == "docs-content" ]]; then
   retryCall ${DEPLOY_RETRIES} ./scripts/deploy/publish-docs-content.sh

scripts/ci/travis-env.sh

@@ -1,11 +0,0 @@
-#!/bin/bash
-
-# If FIREBASE_ACCESS_TOKEN not set yet, export the FIREBASE_ACCESS_TOKEN using the JWT token that
-# Travis generated and exported for SAUCE_ACCESS_KEY.
-# This is a workaround for travis-ci/travis-ci#7223
-# WARNING: FIREBASE_ACCESS_TOKEN should NOT be printed
-export FIREBASE_ACCESS_TOKEN=${FIREBASE_ACCESS_TOKEN:-$SAUCE_ACCESS_KEY}
-
-# - we overwrite the value set by Travis JWT addon here to work around travis-ci/travis-ci#7223
-# for FIREBASE_ACCESS_TOKEN
-export SAUCE_ACCESS_KEY=9b988f434ff8-fbca-8aa4-4ae3-35442987

scripts/ci/travis-testing.sh

@@ -39,17 +39,10 @@ elif is_e2e; then
   xvfb-run -a --server-args='-screen 0, 1024x768x16' $(npm bin)/gulp ci:e2e
 elif is_aot; then
   $(npm bin)/gulp ci:aot
-elif is_payload; then
-  $(npm bin)/gulp ci:payload
 elif is_unit; then
   $(npm bin)/gulp ci:test
 elif is_prerender; then
   $(npm bin)/gulp ci:prerender
 fi
 
-# Upload coverage results if those are present.
-if [ -f dist/coverage/coverage-summary.json ]; then
-  $(npm bin)/gulp ci:coverage
-fi
-
 teardown_tunnel

scripts/deploy/deploy-dashboard.sh

@@ -1,41 +0,0 @@
-#!/bin/bash
-
-# The script should immediately exit if any command in the script fails.
-set -e
-
-# This script deploys the Dashboard App and their Cloud Functions to Firebase.
-# Before deploying, the script installs all dependencies and builds the dashboard app in production.
-
-# Go to the project root directory
-cd $(dirname ${0})/../..
-
-if [ -z ${MATERIAL2_BOARD_FIREBASE_DEPLOY_KEY} ]; then
-  echo "Error: No access token for firebase specified." \
-       "Please set the environment variable 'MATERIAL2_DASHBOARD_ACCESS_TOKEN'."
-  exit 1
-fi
-
-# Paths to the dashboard and functions directories.
-dashboardFolder=tools/dashboard
-
-# Path to the firebase binary of the root package.json
-firebaseBin=$(npm bin)/firebase
-
-# Go to the dashboard folder because otherwise the Firebase CLI tries to deploy the wrong project.
-cd ${dashboardFolder}
-
-# Install node_modules for the dashboard and afterwards build the dashboard app in production.
-(npm install; npm run build-production) &
-
-# Install node modules for dashboard functions. Firebase CLI needs to execute the functions
-# to collect all function names before it can deploy them.
-(cd functions; npm install) &
-
-# The dashboard and function dependencies are installed concurrently. Also the dashboard app is
-# build in production afterwards. Wait for all async tasks to finish before proceeding.
-wait
-
-# Deploy the dashboard to Firebase. Based on the current configuration hosting and functions
-# will be deployed.
-${firebaseBin} deploy --token ${MATERIAL2_BOARD_FIREBASE_DEPLOY_KEY} \
-  --non-interactive --project material2-board