diff options
| author | Lars Wirzenius <liw@liw.fi> | 2018-04-05 10:36:45 +0300 |
|---|---|---|
| committer | Lars Wirzenius <liw@liw.fi> | 2018-04-05 10:36:45 +0300 |
| commit | d1ffc74f48e5bfc4766797c91374d3235b643c62 (patch) | |
| tree | 8682e7cab912c33875ab766799b00b9669ae529b /architecture.mdwn | |
| parent | e3188dcf88b64771736a8a31a04afe75960a4427 (diff) | |
| download | ick.liw.fi-d1ffc74f48e5bfc4766797c91374d3235b643c62.tar.gz | |
Change: clarify ick goals, add artifact store to core concepts
Diffstat (limited to 'architecture.mdwn')
| -rw-r--r-- | architecture.mdwn | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/architecture.mdwn b/architecture.mdwn index e40fa2a..0e88e07 100644 --- a/architecture.mdwn +++ b/architecture.mdwn @@ -42,13 +42,14 @@ Ick aims to be a CI system. It deals with a small number of concepts: program, or to achieve some other goal * **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 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 building packages of any reasonable type. In our wildest dreams it'll be scalable enough to build a full, large Linux distribution such as -Debian. Also, it should be painless to deploy, operate, and use. We'll -see. +Debian. Also, it should be painless to deploy, operate, and use. Example ----------------------------------------------------------------------------- |