rename to "Chipyard"

.circleci/README.md

@@ -1,5 +1,5 @@
-REBAR CI
-========
+Chipyard CI
+===========
 
 Website: https://circleci.com/gh/ucb-bar/project-template
 
@@ -32,17 +32,17 @@ Here the key is built from a string where the `checksum` portion converts the fi
 .circleci directory
 -------------------
 
-This directory contains all the collateral for the REBAR CI to work.
+This directory contains all the collateral for the Chipyard CI to work.
 The following is included:
-    
+
     build-toolchains.sh # build either riscv-tools or esp-tools
     build-verilator.sh  # build verilator
     create-hash.sh      # create hashes of riscv-tools/esp-tools so circleci caching can work
     do-rtl-build.sh     # use verilator to build a sim executable
     config.yml          # main circleci config script to enumerate jobs/workflows
 
-How things are setup for REBAR
-------------------------------
+How things are setup for Chipyard
+---------------------------------
 
 The steps for CI to run are as follows.
 1st, build the toolchains in parallel (note: `esp-tools` is currently not used in the run).

.circleci/build-toolchains.sh

@@ -11,5 +11,5 @@ if [ ! -d "$HOME/$1-install" ]; then
     cd $HOME/
 
     # init all submodules including the tools
-    REBAR_DIR=$HOME/project ./project/scripts/build-toolchains.sh $1
+    CHIPYARD_DIR=$HOME/project ./project/scripts/build-toolchains.sh $1
 fi

.circleci/config.yml

@@ -484,7 +484,7 @@ jobs:
 # Order and dependencies of jobs to run
 workflows:
     version: 2
-    build-and-test-rebar-integration:
+    build-and-test-chipyard-integration:
         jobs:
             # check to make sure commits are on master
             - commit-on-master-check