From 00babbdceae75539b1f62a92f469de672883795d Mon Sep 17 00:00:00 2001 From: Fabian Segatz Date: Wed, 23 Mar 2022 15:11:31 +0100 Subject: [PATCH 1/7] assignment proposal: demonstration for week1: testing & continuous integration --- .../jedma-segatz/pull_request_template.md | 39 +++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 contributions/demo/jedma-segatz/pull_request_template.md diff --git a/contributions/demo/jedma-segatz/pull_request_template.md b/contributions/demo/jedma-segatz/pull_request_template.md new file mode 100644 index 0000000000..e7dc61530d --- /dev/null +++ b/contributions/demo/jedma-segatz/pull_request_template.md @@ -0,0 +1,39 @@ +# Assignment Proposal + +## Title + +Automated testing and delivery for FreeRTOS using AWS + +## Names and KTH ID + - Johan Edman (jedma@kth.se) + - Fabian Segatz (segatz@kth.se) + +## Deadline + +Deadline task 1 + +## Category + +Testing & Continuous Integration + +## Description + +In IoT there are often many devices that should receive updates, even when they are already embedded in field. + +It is crucial to validate the correctness of any update, before it is published. At the same time security updates should be supplied fast, to close eventual weaknesses. Automated testing can be used to reduce the time-to-delivery. + +However, software developement for embedded systems is not as advanced by the means of using CI-pipelines and need some further exploring. + +We plan to give a demonstration on how to use, Jenkins and AWS to automatically deploy firmware which is built upon FreeRTOS. The firmware-under-test runs some schedulability test, which sends back metrics to Jenkins. + +The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. + +## Comment +There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipline for embedded devices was given. + +Our proposal divers in three ways: + 1. We don't use the remote testing suite of plattform io, and instead use AWS. + 2. Deployment with OTA updates, which simulates a better use-case for in-field testing + 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. + + From 1c44023ec8dfefacaef1ee98e6dbad8f5a536c15 Mon Sep 17 00:00:00 2001 From: Fabian Segatz Date: Wed, 23 Mar 2022 15:21:32 +0100 Subject: [PATCH 2/7] Rename markdown file --- .../demo/jedma-segatz/{pull_request_template.md => Readme.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename contributions/demo/jedma-segatz/{pull_request_template.md => Readme.md} (100%) diff --git a/contributions/demo/jedma-segatz/pull_request_template.md b/contributions/demo/jedma-segatz/Readme.md similarity index 100% rename from contributions/demo/jedma-segatz/pull_request_template.md rename to contributions/demo/jedma-segatz/Readme.md From 9577bf0e7a0fb8aed0f83475f331882743b788d5 Mon Sep 17 00:00:00 2001 From: Fabian Segatz Date: Wed, 23 Mar 2022 15:29:38 +0100 Subject: [PATCH 3/7] not ignoring cases anymore --- contributions/demo/jedma-segatz/README.md | 39 +++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 contributions/demo/jedma-segatz/README.md diff --git a/contributions/demo/jedma-segatz/README.md b/contributions/demo/jedma-segatz/README.md new file mode 100644 index 0000000000..e7dc61530d --- /dev/null +++ b/contributions/demo/jedma-segatz/README.md @@ -0,0 +1,39 @@ +# Assignment Proposal + +## Title + +Automated testing and delivery for FreeRTOS using AWS + +## Names and KTH ID + - Johan Edman (jedma@kth.se) + - Fabian Segatz (segatz@kth.se) + +## Deadline + +Deadline task 1 + +## Category + +Testing & Continuous Integration + +## Description + +In IoT there are often many devices that should receive updates, even when they are already embedded in field. + +It is crucial to validate the correctness of any update, before it is published. At the same time security updates should be supplied fast, to close eventual weaknesses. Automated testing can be used to reduce the time-to-delivery. + +However, software developement for embedded systems is not as advanced by the means of using CI-pipelines and need some further exploring. + +We plan to give a demonstration on how to use, Jenkins and AWS to automatically deploy firmware which is built upon FreeRTOS. The firmware-under-test runs some schedulability test, which sends back metrics to Jenkins. + +The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. + +## Comment +There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipline for embedded devices was given. + +Our proposal divers in three ways: + 1. We don't use the remote testing suite of plattform io, and instead use AWS. + 2. Deployment with OTA updates, which simulates a better use-case for in-field testing + 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. + + From 1e5a5ec217cd52045ae3fc35cc18e7c1abeac486 Mon Sep 17 00:00:00 2001 From: Fabian Segatz Date: Wed, 23 Mar 2022 15:33:15 +0100 Subject: [PATCH 4/7] fix titles --- contributions/demo/jedma-segatz/README.md | 6 ++---- contributions/demo/jedma-segatz/Readme.md | 6 ++---- 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/contributions/demo/jedma-segatz/README.md b/contributions/demo/jedma-segatz/README.md index e7dc61530d..54e4575ef2 100644 --- a/contributions/demo/jedma-segatz/README.md +++ b/contributions/demo/jedma-segatz/README.md @@ -28,12 +28,10 @@ We plan to give a demonstration on how to use, Jenkins and AWS to automatically The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. -## Comment +Comment: There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipline for embedded devices was given. Our proposal divers in three ways: 1. We don't use the remote testing suite of plattform io, and instead use AWS. 2. Deployment with OTA updates, which simulates a better use-case for in-field testing - 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. - - + 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. \ No newline at end of file diff --git a/contributions/demo/jedma-segatz/Readme.md b/contributions/demo/jedma-segatz/Readme.md index e7dc61530d..54e4575ef2 100644 --- a/contributions/demo/jedma-segatz/Readme.md +++ b/contributions/demo/jedma-segatz/Readme.md @@ -28,12 +28,10 @@ We plan to give a demonstration on how to use, Jenkins and AWS to automatically The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. -## Comment +Comment: There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipline for embedded devices was given. Our proposal divers in three ways: 1. We don't use the remote testing suite of plattform io, and instead use AWS. 2. Deployment with OTA updates, which simulates a better use-case for in-field testing - 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. - - + 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. \ No newline at end of file From 198122819ab0e4d66a38eaef1c1efc003001831d Mon Sep 17 00:00:00 2001 From: Fabian Segatz <53816763+fsegatz@users.noreply.github.com> Date: Wed, 23 Mar 2022 15:43:46 +0100 Subject: [PATCH 5/7] Delete Readme.md --- contributions/demo/jedma-segatz/Readme.md | 37 ----------------------- 1 file changed, 37 deletions(-) delete mode 100644 contributions/demo/jedma-segatz/Readme.md diff --git a/contributions/demo/jedma-segatz/Readme.md b/contributions/demo/jedma-segatz/Readme.md deleted file mode 100644 index 54e4575ef2..0000000000 --- a/contributions/demo/jedma-segatz/Readme.md +++ /dev/null @@ -1,37 +0,0 @@ -# Assignment Proposal - -## Title - -Automated testing and delivery for FreeRTOS using AWS - -## Names and KTH ID - - Johan Edman (jedma@kth.se) - - Fabian Segatz (segatz@kth.se) - -## Deadline - -Deadline task 1 - -## Category - -Testing & Continuous Integration - -## Description - -In IoT there are often many devices that should receive updates, even when they are already embedded in field. - -It is crucial to validate the correctness of any update, before it is published. At the same time security updates should be supplied fast, to close eventual weaknesses. Automated testing can be used to reduce the time-to-delivery. - -However, software developement for embedded systems is not as advanced by the means of using CI-pipelines and need some further exploring. - -We plan to give a demonstration on how to use, Jenkins and AWS to automatically deploy firmware which is built upon FreeRTOS. The firmware-under-test runs some schedulability test, which sends back metrics to Jenkins. - -The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. - -Comment: -There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipline for embedded devices was given. - -Our proposal divers in three ways: - 1. We don't use the remote testing suite of plattform io, and instead use AWS. - 2. Deployment with OTA updates, which simulates a better use-case for in-field testing - 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. \ No newline at end of file From bfdef2235c6e5737f4b84ced0977e78dc04df3fe Mon Sep 17 00:00:00 2001 From: Fabian Segatz Date: Fri, 25 Mar 2022 10:01:08 +0100 Subject: [PATCH 6/7] put proposal inside week folder --- .../jedma-segatz/README.md | 74 +++++++++---------- 1 file changed, 37 insertions(+), 37 deletions(-) rename contributions/demo/{ => week2-testing-and-CI}/jedma-segatz/README.md (51%) diff --git a/contributions/demo/jedma-segatz/README.md b/contributions/demo/week2-testing-and-CI/jedma-segatz/README.md similarity index 51% rename from contributions/demo/jedma-segatz/README.md rename to contributions/demo/week2-testing-and-CI/jedma-segatz/README.md index 54e4575ef2..f3ebacb751 100644 --- a/contributions/demo/jedma-segatz/README.md +++ b/contributions/demo/week2-testing-and-CI/jedma-segatz/README.md @@ -1,37 +1,37 @@ -# Assignment Proposal - -## Title - -Automated testing and delivery for FreeRTOS using AWS - -## Names and KTH ID - - Johan Edman (jedma@kth.se) - - Fabian Segatz (segatz@kth.se) - -## Deadline - -Deadline task 1 - -## Category - -Testing & Continuous Integration - -## Description - -In IoT there are often many devices that should receive updates, even when they are already embedded in field. - -It is crucial to validate the correctness of any update, before it is published. At the same time security updates should be supplied fast, to close eventual weaknesses. Automated testing can be used to reduce the time-to-delivery. - -However, software developement for embedded systems is not as advanced by the means of using CI-pipelines and need some further exploring. - -We plan to give a demonstration on how to use, Jenkins and AWS to automatically deploy firmware which is built upon FreeRTOS. The firmware-under-test runs some schedulability test, which sends back metrics to Jenkins. - -The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. - -Comment: -There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipline for embedded devices was given. - -Our proposal divers in three ways: - 1. We don't use the remote testing suite of plattform io, and instead use AWS. - 2. Deployment with OTA updates, which simulates a better use-case for in-field testing - 3. Unit testing without using an extra probe device, expoiting the capabilities of RTOS. \ No newline at end of file +# Assignment Proposal + +## Title + +Automated testing and delivery for FreeRTOS using AWS + +## Names and KTH ID + - Johan Edman (jedma@kth.se) + - Fabian Segatz (segatz@kth.se) + +## Deadline + +Task 1 + +## Category + +Demo + +## Description + +In IoT there are often many devices that should receive updates, even when they are already embedded in the field. + +It is crucial to validate the correctness of any update before it is published. At the same time, security updates should be supplied fast, to close eventual weaknesses. Automated testing can be used to reduce the time-to-delivery. + +However, software development for embedded systems is not as advanced by the means of using CI-pipelines and needs some further exploring. + +We plan to give a demonstration on how to use, Jenkins and AWS to automatically deploy firmware that is built upon FreeRTOS. The firmware-under-test runs some schedulability test, which sends back metrics to Jenkins. + +The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. + +## Comment +There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipeline for embedded devices was given. + +Our proposal differs in three ways: + 1. We don't use the remote testing suite of plattformIO, and instead use AWS. + 2. Deployment with OTA updates, which simulates a better use-case for in-field testing + 3. Unit testing without using an extra probe device, exploiting the capabilities of RTOS. \ No newline at end of file From ab47117c2ad8e4eabd520113b46c80f71609ff96 Mon Sep 17 00:00:00 2001 From: Fabian Segatz Date: Fri, 25 Mar 2022 10:04:41 +0100 Subject: [PATCH 7/7] fix schema --- contributions/demo/week2-testing-and-CI/jedma-segatz/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributions/demo/week2-testing-and-CI/jedma-segatz/README.md b/contributions/demo/week2-testing-and-CI/jedma-segatz/README.md index f3ebacb751..479e1ebb58 100644 --- a/contributions/demo/week2-testing-and-CI/jedma-segatz/README.md +++ b/contributions/demo/week2-testing-and-CI/jedma-segatz/README.md @@ -28,7 +28,7 @@ We plan to give a demonstration on how to use, Jenkins and AWS to automatically The deployment is supposed to be performed using over-the-air (OTA) updating to an ESP32 evaluation board connected to the same network as the build server. -## Comment +Comment: There was a similar project in 2020 (https://github.com/KTH/devops-course/tree/2022/attic/2020/contributions-2020/demo/carljen-axelbc), where a demonstration of a CI pipeline for embedded devices was given. Our proposal differs in three ways: