From b024d7e2617e2d08be731dcaa29d69f0b3961f2c Mon Sep 17 00:00:00 2001 From: Huanyi Chen Date: Mon, 26 Feb 2024 12:49:45 -0500 Subject: [PATCH] Add after-action report --- lectures/flipped/L34.md | 5 +++++ lectures/flipped/L35.md | 7 +++++++ 2 files changed, 12 insertions(+) diff --git a/lectures/flipped/L34.md b/lectures/flipped/L34.md index 0903767..5e06efa 100644 --- a/lectures/flipped/L34.md +++ b/lectures/flipped/L34.md @@ -77,3 +77,8 @@ wildlife photography. We went through all the AWS questions (which aren't really discussed in the notes). They are a good set of topics for discussion. Feels like a liberal arts classroom. + +# After-action report, huanyi, 1Apr24 + +We went through some of the questions. Maybe it was like 25 minutes on this +topic? diff --git a/lectures/flipped/L35.md b/lectures/flipped/L35.md index 4fd1061..2ad2eb3 100644 --- a/lectures/flipped/L35.md +++ b/lectures/flipped/L35.md @@ -45,3 +45,10 @@ Did the naming exercise. Did not do the other exercises. Instead, we collectively talked through an example of writing an incident report (fake, "patricklam.ca is down"). That works as an exercise, though maybe one could read an existing incident report also. Or have a better scenario. + +# After-action report, huanyi, 1Apr24 & 5Apr24 + +The xz incident can be extended further I think. On Apr 5th, we tried both +GitHub Action and GitLab CI/CD. UW GitLab needs us to set up a separate runner +to do jobs. I used my own laptop for it. Its tutorial was not very +straightforward.