From 81ee94d782f7829279869fe17abfb7f9d1c33f46 Mon Sep 17 00:00:00 2001 From: Flug0 Date: Thu, 5 Sep 2024 20:08:44 +0200 Subject: [PATCH 1/4] Added demo proposal --- .../demo/week3/hugomal-oschel/README.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 contributions/demo/week3/hugomal-oschel/README.md diff --git a/contributions/demo/week3/hugomal-oschel/README.md b/contributions/demo/week3/hugomal-oschel/README.md new file mode 100644 index 0000000000..c9efdd0a99 --- /dev/null +++ b/contributions/demo/week3/hugomal-oschel/README.md @@ -0,0 +1,27 @@ +# Assignment Proposal + +## Title + +Automating Software Releases with jReleaser and GitHub Actions + +## Names and KTH ID + + - Hugo Malmberg (hugomal@kth.se) + - Oscar Hellgren (oschel@kth.se) + +## Deadline + +- Week 3 + +## Category + +- Demo + +## Description + +We will demonstrate how to automate the software release process using jReleaser and GitHub Actions. The GitHub Actions workflow will be triggered when a new release tag is pushed to the repository. jReleaser will handle tasks such as generating a changelog from commit messages, packaging the software, signing artifacts. + + +**Relevance** + +jReleaser is an emerging tool for automating software releases, making it a valuable addition to any DevOps pipeline. This demo will show how jReleaser can simplify the release process by automating tedious tasks like changelog generation, artifact signing, and multi-platform distribution. Using GitHub Actions for automation further showcases how continuous integration and delivery can be extended to cover the entire lifecycle of a software project, from code changes to final release. From 5446c3cfd57ea5c831cdb0642144caa1b85a4bfa Mon Sep 17 00:00:00 2001 From: flug0 Date: Thu, 3 Oct 2024 16:53:40 +0200 Subject: [PATCH 2/4] Week 7, presentation proposal --- .../week7/hugomal-oschel/README.md | 27 +++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 contributions/presentation/week7/hugomal-oschel/README.md diff --git a/contributions/presentation/week7/hugomal-oschel/README.md b/contributions/presentation/week7/hugomal-oschel/README.md new file mode 100644 index 0000000000..ad3d4325a2 --- /dev/null +++ b/contributions/presentation/week7/hugomal-oschel/README.md @@ -0,0 +1,27 @@ +# Assignment Proposal + +## Title + +Understanding monitoring and its importance for DevOps + +## Names and KTH ID + + - Oscar Hellgren (oschel@kth.se) + - Hugo Malmberg (hugomal@kth.se) + +## Deadline + +- Week 7 + +## Category + +- Presentation + + +## Description + +In this presentation we will explain software bots and how they can be used to monitor platforms, both to quickly spot issues in production and speed up testing. + +**Relevance** + +Getting quick updates on issues is important, especially in production where the consequences can be large. Monitoring can also speed up testing of software, thus decreasing the time from coding to production while keeping high quality. \ No newline at end of file From 6fee1f553f36bb52c648ba4a2980abe86cecd790 Mon Sep 17 00:00:00 2001 From: Flug0 <92332371+Flug0@users.noreply.github.com> Date: Fri, 4 Oct 2024 22:59:17 +0200 Subject: [PATCH 3/4] Update title --- contributions/presentation/week7/hugomal-oschel/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contributions/presentation/week7/hugomal-oschel/README.md b/contributions/presentation/week7/hugomal-oschel/README.md index ad3d4325a2..5e4837b1a6 100644 --- a/contributions/presentation/week7/hugomal-oschel/README.md +++ b/contributions/presentation/week7/hugomal-oschel/README.md @@ -2,7 +2,7 @@ ## Title -Understanding monitoring and its importance for DevOps +ChatOps Bots for Monitoring and Incident Response in DevOps ## Names and KTH ID @@ -24,4 +24,4 @@ In this presentation we will explain software bots and how they can be used to m **Relevance** -Getting quick updates on issues is important, especially in production where the consequences can be large. Monitoring can also speed up testing of software, thus decreasing the time from coding to production while keeping high quality. \ No newline at end of file +Getting quick updates on issues is important, especially in production where the consequences can be large. Monitoring can also speed up testing of software, thus decreasing the time from coding to production while keeping high quality. From 2f4a02da2a07d88a99aa274a13a568535cfd9160 Mon Sep 17 00:00:00 2001 From: flug0 Date: Thu, 17 Oct 2024 16:48:24 +0200 Subject: [PATCH 4/4] added feedback --- .../feedback/hugomal-oscols/README.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 contributions/feedback/hugomal-oscols/README.md diff --git a/contributions/feedback/hugomal-oscols/README.md b/contributions/feedback/hugomal-oscols/README.md new file mode 100644 index 0000000000..3c1281cc3d --- /dev/null +++ b/contributions/feedback/hugomal-oscols/README.md @@ -0,0 +1,22 @@ +# Assignment Proposal + +## Title + +Feedback on "Profiling Python Applications Without Modifying Code With Py-Spy". + +## Names and KTH ID + +- Hugo Malmberg (hugomal@kth.se) +- Oscar Olsson (oscols@kth.se) + +## Deadline + +- Task 3 + +## Category + +- Feedback + +## Description + +Feedback for the tutorial can be found [here](https://github.com/KTH/devops-course/pull/2651#issuecomment-2419718548).