Change spec for cleanly for CI builds

We will be requiring the --ci option for CI builds, and we need to
tell cleanly the build number and the target's Debian release, so that
cleanly can produce version numbers accordingly.

1 files changed, 10 insertions, 8 deletions

diff --git a/doc/060-cleanly.yarn b/doc/060-cleanly.yarn
index 167e171..72ee1a4 100644
--- a/doc/060-cleanly.yarn
+++ b/doc/060-cleanly.yarn
@@ -26,8 +26,8 @@ what the name of the project is and what its version is.
 We create a tar archive by extracing the source code from git. The
 operation needs to know the upstream name and version number.
 
-    WHEN user runs, in foo, cleanly tarball
-    THEN file foo-3.2.tar.xz exists
+    WHEN user runs, in foo, cleanly --ci --buildno 42 tarball
+    THEN file foo-3.2.ci42.tar.xz exists
 
 ## Create Debian source package
 
@@ -36,10 +36,11 @@ provides the Debian packaging files in the same branch and that the
 Debian version part is just 1. (FIXME: This will need to be made more
 flexible later.)
 
-    WHEN user runs, in foo, cleanly dsc
-    THEN file foo_3.2.orig.tar.xz exists
-    AND file foo_3.2-1.debian.tar.xz exists
-    AND file foo_3.2-1.dsc exists
+    WHEN user runs, in foo,
+    ... cleanly --ci --buildno 42 --debian-release debian7 dsc
+    THEN file foo_3.2.ci42.orig.tar.xz exists
+    AND file foo_3.2.ci42-1.debian7.debian.tar.xz exists
+    AND file foo_3.2.ci42-1.debian7.dsc exists
 
 ## Build a Debian binary package
 
@@ -47,5 +48,6 @@ This is where things get interesting. We build a Debian binary
 package, given a source package. (Note that for this, we fake the
 actual build to avoid having to have `root` access.)
 
-    WHEN user runs, in foo, cleanly deb
-    THEN file foo_3.2-1_all.deb exists
+    WHEN user runs, in foo,
+    ... cleanly --ci --buildno 42 --debian-release debian7 deb
+    THEN file foo_3.2.ci42-1.debian7_all.deb exists