summaryrefslogtreecommitdiff
path: root/icktool.mdwn
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2018-06-18 16:09:03 +0300
committerLars Wirzenius <liw@liw.fi>2018-06-18 16:09:03 +0300
commit2be69d3e4aceb8ca40e199a907236a2ff4a8e731 (patch)
treedffbb5959354714ff320f6f3056446180176f1f4 /icktool.mdwn
parentad6c64bec44d038dbd40529136e7eb1278cf890d (diff)
downloadick.liw.fi-2be69d3e4aceb8ca40e199a907236a2ff4a8e731.tar.gz
Add: some general advice
Diffstat (limited to 'icktool.mdwn')
-rw-r--r--icktool.mdwn21
1 files changed, 21 insertions, 0 deletions
diff --git a/icktool.mdwn b/icktool.mdwn
index 40a9f4c..1e3d986 100644
--- a/icktool.mdwn
+++ b/icktool.mdwn
@@ -252,3 +252,24 @@ Example .ick files
The <http://git.liw.fi/liw-ci/tree/> repository has some .ick files,
used by ick's author for his personal instances.
+
+
+General advice
+-----------------------------------------------------------------------------
+
+On each ick instance, set up one or more projects that build systrees.
+Build one for each target Debian release: `jessie`, `stretch`,
+`unstable`, etc. Build each of these projects to populate the artifact
+store with systree artifacts. Each actual project should use one of
+the artifacts to do the build in a container.
+
+When building in a container, you can install more things inside the
+container. If you build repeatedly, it may be worth having more than
+just the minimal container. Instead have an artifact with all the
+build dependencies installed, so each build does not have to start
+with installing them, saving time.
+
+Ick can build several things at once. As many things as there are
+workers. However, each build (currently) runs on one worker.
+
+There's currently no way to stop a triggered build.