diff options
| author | Lars Wirzenius <liw@liw.fi> | 2018-06-09 13:39:36 +0300 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2018-06-09 13:39:36 +0300 |
| commit | ad071aaa2b6e50b996a14895f7c6bd098a019d1d (patch) | |
| tree | c86facba28a1277f212a4f9db1852a3e0d654801 /architecture.mdwn | |
| parent | 8929aaf0c92bceb621e4d3728ba97e24d7a6fe23 (diff) | |
| download | ick.liw.fi-ad071aaa2b6e50b996a14895f7c6bd098a019d1d.tar.gz | |
Change: clarify Overview section
Diffstat (limited to 'architecture.mdwn')
| -rw-r--r-- | architecture.mdwn | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/architecture.mdwn b/architecture.mdwn index 4efd49b..9c1af8b 100644 --- a/architecture.mdwn +++ b/architecture.mdwn @@ -65,25 +65,25 @@ to name the first generation "ick". Overview ----------------------------------------------------------------------------- -A continuous integration (CI) or continuous deployment (CD) system is, -at its most simple core, an automated system that reacts to changes in -a program's source code by doing a build of the program, running any -of its automated tests, and then publishing the results somewhere. A -CD system continues from there to also installing the new version of -the program on all relevant computers. If a build or an automated test -fails, the system notifies the relevant parties. +A continuous integration system is, at its most simple core, an +automated system that reacts to changes in a program's source code by +doing a build of the program, running any of its automated tests, and +then publishing the results somewhere. A continuoues deployment system +continues from there to also installing the new version of the program +on all relevant computers. If any step in the process fails, the +system notifies the relevant parties. Ick aims to be a CI system. It deals with a small number of concepts: * **projects**, which consist of **source code** in a version control system -* **pipelines**, which are reuseable sequences of steps aiming to - convert source code into something executable, or to test the - program, or to achieve some other goal +* **pipelines**, which are reuseable sequences of actions aiming to + achieve some task (build program source code, run tests, etc) * **workers**, which do all the actual work by executing pipeline actions * **artifact store**, which holds results of project builds, and intermediary results used by the build +* **identity provider**, which handles authentication of users The long-term goal for ick is to provide a CI/CD system that can be used to build and deploy any reasonable software project, including |