From f70d6c0442f8f2f01a8195f439fddc6c0831a905 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Sat, 1 Jul 2017 13:06:36 +0300 Subject: Add: controller build scenario This scenario test the ick2 MVP controller API. See http://ick-devel.liw.fi/f6166c07380e4cc78b5619d8c1322736.html for more detailed information. --- yarns/000.yarn | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 yarns/000.yarn (limited to 'yarns/000.yarn') diff --git a/yarns/000.yarn b/yarns/000.yarn new file mode 100644 index 0000000..7a19824 --- /dev/null +++ b/yarns/000.yarn @@ -0,0 +1,24 @@ +--- +title: Ick2 controller yarns +... + + +Introduction +============================================================================= + +Ick2 will be a continuous integration system. Its core component is +the **controller**, which does nothing, except decides what workers should +do. It knows of the projects that can be built, and keeps track what +step is being run on each project, and collects build output from the +workers. + +This document specifies the yarn test scenarios for a minimal viable +version of the controller: there will be a small number of project, +each project builds a web site from source in git, using ikiwiki, and +publishes the website on a server using rsync. + +The controller provides an HTTP API for controlling a build. The API +is used by an external entity (such as the git server) to trigger a +build, and by workers or worker proxies to request something to do, +and to report results. The API may also eventually be used by end +users to query status and results. -- cgit v1.2.1