From ea2ae9dd16df4f4c917d0cf2d315419236c43134 Mon Sep 17 00:00:00 2001 From: Rikard Johansson Date: Fri, 30 Aug 2024 13:56:36 +0200 Subject: [PATCH 1/3] Week2: Presentation proposal --- .../presentation/week2/rikj-hocker/README.md | 29 +++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 contributions/presentation/week2/rikj-hocker/README.md diff --git a/contributions/presentation/week2/rikj-hocker/README.md b/contributions/presentation/week2/rikj-hocker/README.md new file mode 100644 index 0000000000..215a917412 --- /dev/null +++ b/contributions/presentation/week2/rikj-hocker/README.md @@ -0,0 +1,29 @@ +# Assignment Proposal + +## Title + +Introducing Team City pipelines a CI/CD tool for samll, mid-sized dev teams by JetBrains + +## Names and KTH ID + + - Rikard Johansson (rikj@kth.se) + - Simon Hocker (hocker@kth.se) + +## Deadline +- Week 2 + +## Category +- Presentation + +## Description + +We want to present a hot new CI/CD called TeamCity Pipelines, a tool that is developed by a well know software development company JetBrains who are famous for their Intellij IDE, Kotlin programming language and Ktor backend service and so forth. Most CI/CD tools are developed with the intention fo being utilised by large organisations, streamlining the development process for enterprise teams, but this new software aims to simplify the process for smaller teams who may wish for less complexity and more recommendations straight from the start. + +**Relevance** + +Larger CI/CD solutions usually require dedicated staff members for maintaining and administering their pipelines, whereas a smaller team would have to handle it all on their own, and thus a simplified solution can save them a great deal of time. For smaller development teams in the sizes of maybe a dozen, more efficient CI/CD solutions are growing in demand. Considering JetBrains prestigious pedigree for developing industry standard softwares as mentioned previously, it is not unlikely that TeamCity Pipelines will make a noteworthy impact on the small team development lifestyle. + +Usually, example based testing is used when writing unit tests, where the programmer has to come up with various test inputs and define what the expected results are. +This is tedious and error-prone in the long run, thus one can utilize property-based testing to speed up the processes. +Property-based testing also explores more inputs and conditions, which makes it easier to uncover edge cases. +This is relevant to DevOps as it concerns test automation as well as being able to significantly enhance the testing suite. From c135a4797cbb7c087a8b1f06e4a4a606a5dc791c Mon Sep 17 00:00:00 2001 From: Rikard Johansson Date: Fri, 30 Aug 2024 13:58:42 +0200 Subject: [PATCH 2/3] Remove unneccesary paragraph --- contributions/presentation/week2/rikj-hocker/README.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/contributions/presentation/week2/rikj-hocker/README.md b/contributions/presentation/week2/rikj-hocker/README.md index 215a917412..857f3a3113 100644 --- a/contributions/presentation/week2/rikj-hocker/README.md +++ b/contributions/presentation/week2/rikj-hocker/README.md @@ -22,8 +22,3 @@ We want to present a hot new CI/CD called TeamCity Pipelines, a tool that is dev **Relevance** Larger CI/CD solutions usually require dedicated staff members for maintaining and administering their pipelines, whereas a smaller team would have to handle it all on their own, and thus a simplified solution can save them a great deal of time. For smaller development teams in the sizes of maybe a dozen, more efficient CI/CD solutions are growing in demand. Considering JetBrains prestigious pedigree for developing industry standard softwares as mentioned previously, it is not unlikely that TeamCity Pipelines will make a noteworthy impact on the small team development lifestyle. - -Usually, example based testing is used when writing unit tests, where the programmer has to come up with various test inputs and define what the expected results are. -This is tedious and error-prone in the long run, thus one can utilize property-based testing to speed up the processes. -Property-based testing also explores more inputs and conditions, which makes it easier to uncover edge cases. -This is relevant to DevOps as it concerns test automation as well as being able to significantly enhance the testing suite. From 5a890fc0d98d9e371297b10b8cff87d3322c7146 Mon Sep 17 00:00:00 2001 From: Rikard Johansson Date: Fri, 6 Sep 2024 01:29:14 +0200 Subject: [PATCH 3/3] Week3: Demo proposal --- .../demo/week3/rikj-millear/README.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 contributions/demo/week3/rikj-millear/README.md diff --git a/contributions/demo/week3/rikj-millear/README.md b/contributions/demo/week3/rikj-millear/README.md new file mode 100644 index 0000000000..4fe4701140 --- /dev/null +++ b/contributions/demo/week3/rikj-millear/README.md @@ -0,0 +1,26 @@ +# Assignment Proposal + +## Title + +Gitlab CI/CD workflow for deploying fullstack web application on self-hosted server via docker. + +## Names and KTH ID + + - Rikard Johansson (rikj@kth.se) + - Mille Af Rolén (millear@kth.se) + +## Deadline + +- Week 3 + +## Category + +- Demo + +## Description + +In this demo, we will walk you through configuring GitLab CI/CD for the automated deployment of a full-stack web application on a self-hosted server using Docker. We will cover the prerequisites, CI/CD variables, setting up a Docker image, installing necessary packages, SSH access to the server, and pulling the latest Docker container to recreate the application. + +**Relevance** + +This demo is relevant because it demonstrates how to streamline the deployment process using GitLab CI/CD, on a self hosted server. Automating the deployment of a full-stack web application reduces manual effort. By integrating Docker, it enhances portability and scalability, allowing developers to deploy applications seamlessly to self-hosted servers or other environments. \ No newline at end of file