From: Richard W.M. Jones <rjones@redhat.com>
Date: Wed, 9 Oct 2013 12:07:31 +0000 (+0100)
Subject: docs: Document how to use onrun + memory_set.
X-Git-Tag: 0.2~3
X-Git-Url: http://git.annexia.org/?a=commitdiff_plain;h=d6fddcd8789aa150d8c65d45a301df2a77a0686c;p=goaljobs.git

docs: Document how to use onrun + memory_set.
---

diff --git a/goaljobs-reference.pod b/goaljobs-reference.pod
index 2ca27c7..da98946 100644
--- a/goaljobs-reference.pod
+++ b/goaljobs-reference.pod
@@ -279,6 +279,7 @@ sees one it will ensure it passes the tests:
  let goal git_commit_tested commit =
    let key = sprintf "repo-tested-%s" commit in
    target (memory_exists key);
+   onrun (fun () -> memory_set key "1");
  
    sh "
      git clone %s test
@@ -286,10 +287,7 @@ sees one it will ensure it passes the tests:
      ./configure
      make
      make check
-   " repo_url;
-
-   (* Record that this commit was tested successfully. *)
-   memory_set key "1"
+   " repo_url
  
  every 30 minutes (fun () ->
    let commit = shout "cd %s && git rev-parse HEAD" repo in
@@ -370,10 +368,9 @@ A common pattern is:
 let goal tested version =
   let key = "myapp-tested-" ^ version in
   target (memory_exists key);
+  onrun (fun () -> memory_set key "1");
  
   (* some code to test this version *)
- 
-  memory_set key "1"
 
 Note in that example the value C<1> is arbitrary.  You just want to
 store I<any> value so that a later call to C<memory_exists> will