forked from KTH/devops-course
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge github.com:KTH/devops-course into 2021
* github.com:KTH/devops-course: (127 commits) Updated Demo: Setting up Drone CI with Bitbucket (KTH#1322) added presentation slides. (KTH#1302) [Submission] Executable tutorial: CI workflow using GitHub Actions for Node.js, Express app, Jest and ESLint (KTH#1269) Tutorial proposal update change (oldPR: KTH#1163) (KTH#1313) Added important information to README (KTH#1309) Course Automation Proposal: Labelizing "feedbackable" merged PR contributions (KTH#1306) Presentation : DevOps adoption in large Enterprise through Continuous Testing (KTH#1285) Delete contributions/presentation/week3/renanb-ved.megha directory (KTH#1300) Awesome guest lecturer for week 6 Change folder name (KTH#1289) Final Submission - Course Automation: Checking Open-Source Requirements (KTH#1299) Feedback Proposal on Executable Tutorial KTH#1278 (KTH#1292) Revert "Final Submission - Course Automation: Checking Open-Source Requirements (KTH#1068)" (KTH#1298) Final Submission - Course Automation: Checking Open-Source Requirements (KTH#1068) Presentation Proposal: Managing secrets in dynamic environments with HashiCorp Vault (KTH#1282) Update README.md Amend students involved in tutorial (KTH#1262) Withdraw proposal KTH#1201 (KTH#1280) Executable tutorial proposal: Integrating Code Climate in developers workflow with shell scripts and docker (KTH#1278) Feedback proposal on KTH#1134: Deploying scheduled functions on Kubernetes using Kubeless (KTH#1273) ...
- Loading branch information
Showing
114 changed files
with
1,914 additions
and
126 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,68 @@ | ||
| borzi | ||
| sestak | ||
| marwask | ||
| anhenri | ||
| lazarc | ||
| gdba | ||
| despinoy | ||
| fbjorkma | ||
| cjgst | ||
| swill | ||
| sebene | ||
| ericvi | ||
| renanb | ||
| brogard | ||
| johlin5 | ||
| joarr | ||
| kultala | ||
| eryman | ||
| kunwu | ||
| alekru | ||
| johhamm | ||
| johennin | ||
| atema | ||
| andnil5 | ||
| kittyt | ||
| isacarv | ||
| stahr | ||
| augustjo | ||
| karrby | ||
| carllei | ||
| urama | ||
| gchang | ||
| frnorlin | ||
| shapour | ||
| alexdiaz | ||
| fseifert | ||
| agnespet | ||
| aatif | ||
| abwogi | ||
| mwesslen | ||
| henrlind | ||
| linusri | ||
| majate | ||
| kalpet | ||
| ramtinet | ||
| manande | ||
| ntas | ||
| lerjevik | ||
| amarh | ||
| fwallb | ||
| axp | ||
| taqui | ||
| arieltan | ||
| axelelm | ||
| agnesfo | ||
| zangis | ||
| oscarekh | ||
| chrigu | ||
| carinawi | ||
| aronber | ||
| oskstr | ||
| damne | ||
| nwessman | ||
| yuxinm | ||
| isakha | ||
| kallem | ||
| yuehao | ||
| lukasgut |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| # Course automation proposal: check criterion for groups with 3 students. | ||
|
|
||
| ## Members | ||
| Agnes Forsberg (agnesfo@kth.se) | ||
| github: agnesforsberg | ||
|
|
||
| Elin Ryman (eryman@kth.se) | ||
| github: rymane | ||
|
|
||
| ### Group rules in this course regarding groups with 3 student. | ||
| "We recommend 2 students. Three is also possible for ambitious essays, demos or contribution to open-source." | ||
|
|
||
| ## Proposal | ||
| Since a group of 3 students has some extra criterion to fulfill than the regular group of 1-2 students, | ||
| we want to simplify the TAs job in deciding whether the criterion is met. We would like to create a Github Action | ||
| that automatically adds a label to the pull request when the group consists of 3 students. This is for the TA to know | ||
| which pull requests should be ambitious enough. We will also check that the pull request submitted is regarding essays, | ||
| demos or contributions to open-source since those categories are the only allowed for 3 students. | ||
| The Github Action should create a PR comment with information about if 3 students are ok for the chosen category. | ||
|
|
||
| We aim to fulfill the following criterion: | ||
|
|
||
| | | Yes | No | Remarkable | | ||
| |-------------------------------------------- | ----|----|-------------| | ||
| |The work is done before April 6, 2021 (in order to be useful for the course) | Yes | **No** | n-a| | ||
| |The automation task produces a PR status or issue / PR comment | **Yes**, PR comment and adds a label | No | Points to a generated page with valuable additional information | | ||
| |The automation task is reusable | **Yes (next year for this course)** | No | In other courses than this one | | ||
| |The task runs on a standard platform | **Yes**, will use Github action | No | Other platforms (e.g. Moodle, Canvas) | | ||
| |The task is praised by the other students of this course | Yes | No | n-a | | ||
| |The code for the task is available | **Yes**, will use a public repo | No | **Well documented repo** | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,24 @@ | ||
| # GitHub action to show what is available for feedback | ||
|
|
||
| ## Member | ||
|
|
||
| Hilaire Bouaddi, bouaddi@kth.se [https://github.com/Hilaire-Bouaddi] | ||
|
|
||
| ## Rationale | ||
|
|
||
| It takes some minutes to check if a contribution we are interested in will receive feedback or not. This can generate frustration. | ||
| The aim of the proposal is to automate the labelization of PR to mark the ones that can be feedbacked. | ||
|
|
||
| ## Proposal | ||
|
|
||
| I would like to try to create a GitHub Action. This action would: | ||
| - get the URL of every merged PR for contributions in either essay or executable tutorial. | ||
| - for every URL | ||
| - if the URL is referenced in a contribution for feedback, put the label "feedbacked" to the PR, delete other labels "feedbackable" and "feedback claimed" | ||
| - else if the URL is referenced in a feedback PR that waits to be merged, put the label "feedback claimed" to the PR, delete other labels "feedbackable" and "feedbacked" | ||
| - else put the label "feedbackable" to the PR, delete other labels "feedback claimed" and "feedbacked" | ||
|
|
||
| ### Legend | ||
| * "feedbackable": nobody claimed the feedback for this task yet | ||
| * "feedback claimed": a PR is waiting to be merged for the feedback of this contribution | ||
| * "feedbacked": the feedback for this contribution has been claimed |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,66 @@ | ||
| name: Markdown content and change location validation | ||
|
|
||
| on: pull_request | ||
|
|
||
| jobs: | ||
| build: | ||
|
|
||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - uses: actions/checkout@v2 | ||
|
|
||
| - id: changed-files | ||
| name: Get changed files | ||
| uses: jitterbit/get-changed-files@v1 | ||
|
|
||
| - name: Verify submission details | ||
| uses: bubriks/KTH-Course-content-verifier@master | ||
| with: | ||
| location: ^contributions/(.+)/(.+)/ | ||
| changes: ${{ steps.changed-files.outputs.all }} | ||
| structure: > | ||
| { | ||
| "title": [ | ||
| "^# presentation:.*$", | ||
| "^# essay:.*$", | ||
| "^# demo:.*$", | ||
| "^# open-source:.*$", | ||
| "^# executable tutorial:.*$", | ||
| "^# course automation:.*$", | ||
| "^# feedback:.*$" | ||
| ], | ||
| "member": { | ||
| "title": "^## members$", | ||
| "memberOne": [ | ||
| { | ||
| "nameAndEmail": "^[a-z]+( [a-z]+)* [a-z]+ \([a-z]+@kth.se\)$", | ||
| "gitHub": "^github: https://github.com/[a-z]+$" | ||
| }, | ||
| { | ||
| "nameAndEmail": "^[a-z]+( [a-z]+)* [a-z]+ \([a-z]+@kth.se\)$" | ||
| } | ||
| ], | ||
| "memberTwo": [ | ||
| { | ||
| "nameAndEmail": "^[a-z]+( [a-z]+)* [a-z]+ \([a-z]+@kth.se\)$", | ||
| "gitHub": "^github: https://github.com/[a-z]+$" | ||
| }, | ||
| { | ||
| "nameAndEmail": "^[a-z]+( [a-z]+)* [a-z]+ \([a-z]+@kth.se\)$" | ||
| }, | ||
| {} | ||
| ], | ||
| "memberThree": [ | ||
| { | ||
| "nameAndEmail": "^[a-z]+( [a-z]+)* [a-z]+ \([a-z]+@kth.se\)$", | ||
| "gitHub": "^github: https://github.com/[a-z]+$" | ||
| }, | ||
| { | ||
| "nameAndEmail": "^[a-z]+( [a-z]+)* [a-z]+ \([a-z]+@kth.se\)$" | ||
| }, | ||
| {} | ||
| ] | ||
| }, | ||
| "proposal": "^## proposal$" | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,23 +1,43 @@ | ||
| # DEMO 🎥 : Testing and running Github actions locally with Act | ||
| # DEMO 🎥 : Testing and running Github actions locally with Nektos Act | ||
|
|
||
| ## Members | ||
| Anna Nikolskaya (annnik@kth.se) | ||
|
|
||
| Github username: annsudo | ||
|
|
||
| ## Problem area within DevOps | ||
| To test you scripts for custom-written github actions you are forced to push them to the github. That is time consuming and unproductive. | ||
| To test you scripts for custom-written github actions you are forced to push them to the github 🤦♀️ That is time consuming and unproductive! | ||
|
|
||
| ## Solution to it | ||
| with help of open source project Act you can test and debug your actions locally | ||
| with help of open source project Nektos Act and Docker you can run, test and debug your actions locally! | ||
|
|
||
| ## Agenda for demo (Preliminary) | ||
| ## Agenda for demo | ||
|
|
||
| - ✅ How Act work | ||
| - ✅ Installing Act | ||
| - ✅ Several basic comands to run you github action locally | ||
| - ✅ Handeling Secretes | ||
| - ✅ Usage | ||
| - ✅ Handling Secretes | ||
| - ✅ Let´s run it together | ||
| - ✅ Take away | ||
|
|
||
| ## Youtube | ||
| [To the Demo](https://youtu.be/5mYUMxHOjI4) | ||
|
|
||
| ## Code repo of the example-action | ||
| [Action code](https://github.com/annsudo/discord-comments) | ||
|
|
||
| ## Aiming for | ||
| 💥 Remarkable 💥 | ||
|
|
||
|
|
||
|
|
||
| | | Yes | No | Remarkable | | ||
| |-------------------------------------------- | ----|----|-------------| | ||
| |The demonstration is clearly motivated (why it matters for Devops?) | 💥 Yes | No | 💥 Relates to a hard problem | | ||
| |The demonstration is difficult to do | 💥 Yes | No | Relies on a non trivial infrastructure | | ||
| |The demonstration is original | 💥 Yes | No | 💥 The are less than 10 demos on the topic on Internet | | ||
| |The video is sublime (eg visually appealing) | Yes | No | 💥 Excellent narrative | | ||
| |The video contains an [easter egg](https://github.com/OrkoHunter/python-easter-eggs) | Yes |💥 No | Related to the demo | | ||
| |There is a code repo to run the demo | 💥 Yes | No | 💥 Code repo with a solid readme | | ||
| |The video must contain subtitles which are clear and in proper English | 💥 Yes | No | 💥 Clearly understandable voice over | | ||
| |The video includes a take-home message | 💥 Yes | No | 💥 Actionable takeaway | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| # Monitoring availability using Cloudprobe and Prometheus | ||
|
|
||
| ## Members | ||
|
|
||
| Martijn Atema, atema@kth.se, GitHub: Atema | ||
| Simon Persson, siper@kth.se, GitHub: altaired | ||
|
|
||
| ## Proposal | ||
|
|
||
| After building software that users depend on every day it becomes clear that uptime and response times are very important measures to always keep track of. We need to be able to respond quickly when something goes wrong, and want to know when an endpoint doesn't work; preferably before the user even notices. There are some paid, closed-source tools that achieve this, but there's very few self-hosted, open-source alternatives. | ||
|
|
||
| [Cloudprober](https://cloudprober.org) is a good option; it is an open-source monitoring tool that makes it easy to monitor availability and performance of applications. In this demo we will show how to setup Cloudprober to monitor an API and then display the data in [Prometheus](https://prometheus.io). |
Oops, something went wrong.