GitHub/quartz
1
0
Fork 2
mirror of https://github.com/jackyzha0/quartz.git synced 2025-12-23 21:04:07 -06:00
Code Issues Actions Packages Projects Releases Wiki Activity

auto update

Browse Source
This commit is contained in:
Jet Hughes 2022-04-09 17:11:01 +12:00
parent 7bdddf13db
commit 5d28721cbe
3 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
content/daily_notes/2022-04-09.md
View File

@ -15,6 +15,7 @@ Toys In The Attic - Aerosmith - spotify:album:36IxIOGEBAXVozDSiVs09B
- [ ] Assignment 3 - [ ] Assignment 3
- [ ] Cosc201 Tutorial - [ ] Cosc201 Tutorial
- [ ] inquire about dataview in quartz - [ ] inquire about dataview in quartz
- [ ] review notes
- [ ] Cosc201 Lab Shuffle - [ ] Cosc201 Lab Shuffle
## 1.2 Lecture/Labs ## 1.2 Lecture/Labs

0
content/notes/Untitled.md Normal file
View File

5
content/notes/continuous-integration-draft.md
View File

@ -5,16 +5,21 @@ tags:
- cosc202 - cosc202
--- ---
# Overview
Continuous integration (CI) is the practice of automating the integration of code changes from multiple contributors into a single software project - [atlassian](https://www.atlassian.com/continuous-delivery/continuous-integration) . It allows you to automatically run tests, builds, etc when the code is changed. Continuous integration (CI) is the practice of automating the integration of code changes from multiple contributors into a single software project - [atlassian](https://www.atlassian.com/continuous-delivery/continuous-integration) . It allows you to automatically run tests, builds, etc when the code is changed.
# Pipelines, stages, jobs
A continous integration can be defined as a *Pipeline* with several *stages*, each stage with several *jobs* A continous integration can be defined as a *Pipeline* with several *stages*, each stage with several *jobs*
A continuous integration pipeline will run whenever it is triggered. It can be triggered on a schedule, manually, or whenever code is changed. These pipelines run *asynchronously* i.e., the dev doesnt't have to wait for it to complete. A continuous integration pipeline will run whenever it is triggered. It can be triggered on a schedule, manually, or whenever code is changed. These pipelines run *asynchronously* i.e., the dev doesnt't have to wait for it to complete.
# Triggers
Pipelines can also be run locally, and can be triggered, as you, commit, save, type etc. Pipelines can also be run locally, and can be triggered, as you, commit, save, type etc.
# Output
Pipeline can produce several forms of asynchonous output such as email notifications, web badges, webhooks, etc. In addition, most VCS hosting platforms capture the terminal logs from the CI scripts. Pipeline can produce several forms of asynchonous output such as email notifications, web badges, webhooks, etc. In addition, most VCS hosting platforms capture the terminal logs from the CI scripts.
# How to create
Most CI frameworks use YAML for configuration. YAML has a structured text based format similar to python and json Most CI frameworks use YAML for configuration. YAML has a structured text based format similar to python and json
The CI config (in gitlab it is named `.gitlab-ci.yaml`) file goes in the top level of the repo, and is version-managed. This file specifies the stages and jobs of a pipeline, as well as indicating where the output should go. The CI config (in gitlab it is named `.gitlab-ci.yaml`) file goes in the top level of the repo, and is version-managed. This file specifies the stages and jobs of a pipeline, as well as indicating where the output should go.