build: Update build system to use ci.yml [PT-186628316]

.github/workflows/ci.yml

@@ -0,0 +1,41 @@
+name: Continuous Integration
+
+on: push
+
+jobs:
+  jest:
+    name: Build and Run Jest Tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '16'
+      - name: Install Dependencies
+        run: npm ci
+      - name: Build Project
+        run: npm run build
+      - name: Run Jest Tests w/ Coverage
+        run: npm run test:coverage -- --runInBand
+  s3-deploy:
+    name: S3 Deploy
+    needs:
+      - jest
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '16'
+      - name: Install Depndencies
+        run: npm ci
+      - uses: concord-consortium/s3-deploy-action@v1
+        with:
+          bucket: models-resources
+          prefix: ${{ github.event.repository.name }} # cloud-file-manager
+          awsAccessKeyId: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          awsSecretAccessKey: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          # Parameters to GHActions have to be strings, so a regular yaml array cannot
+          # be used. Instead the `|` turns the following lines into a string
+          topBranches: |
+            ["${{ github.event.repository.default_branch }}"]

readme.md

@@ -28,15 +28,19 @@ More info:
 
 ## Deployment
 
-This repository will automatically deploy to S3 using Travis build hooks.
-See `s3_deploy.sh` and `s3_website.yml`
+Deployments are based on the contents of the /dist folder and are built automatically by GitHub Actions for each branch and tag pushed to GitHub.
 
-By default this deploys to models-resources/cloud-file-manager/branch/<branch-name>/
-You can preview thse deployments from a web browser at:
-https://cloud-file-manager.concord.org/branch/<branch-name>/
+Branches are deployed to `https://cloud-file-manager.concord.org/branch/<name>/`.
 
-As of 2020-04-22 pushing the `production` branch will update the production
-version of the CFM app.
+Tags are deployed to `https://cloud-file-manager.concord.org/version/<name>/`
+
+You can view the status of all the branch and tag deploys [here](https://github.com/concord-consortium/cloud-file-manager/actions).
+
+The production release is available at `https://cloud-file-manager.concord.org`.
+
+Production releases are done using a manual GitHub Actions workflow. You specify which tag you want to release to production and the workflow copies that tag's `index-top.html` to `https://cloud-file-manager.concord.org/index.html`.
+
+See the CLUE [docs/deploy.md](https://github.com/concord-consortium/collaborative-learning/blob/master/docs/deploy.md) for more details (it uses the same process).
 
 ## Integrating Cloud File Manager