update README to use chaining/always-chaining, update sample pipeline

README.md

@@ -20,10 +20,11 @@ browser.
 
 ; the build-step you put in your pipeline: first build artifacts, then publish them
 (defn some-build-step [args ctx]
-  (step-support/chain args ctx
-    (produce-output)
-    (artifacts/publish-artifacts (:cwd args) [#"report-folder/.*"
-                                              "some-folder/someBinary.jar"])))
+  (step-support/chaining args ctx ; use always-chaining if you want the artifact even if previous steps failed (e.g. for test reports)
+    (produce-output injected-args injected-ctx)
+    (artifacts/publish-artifacts injected-args injected-ctx
+                                 (:cwd injected-args) [#"report-folder/.*"
+                                                       "some-folder/someBinary.jar"])))
 
 ; url prefix where your artifacts will be available
 (def artifacts-path-context "/artifacts")

project.clj

@@ -7,7 +7,7 @@
                         ["releases" :clojars]]
   :dependencies [[org.clojure/clojure "1.7.0"]
                  [compojure "1.1.8"]
-                 [lambdacd "0.7.0"]]
+                 [lambdacd "0.9.0"]]
   :test2junit-run-ant true
   :profiles {:dev {:dependencies [[ring-server "0.3.1"]
                                   [ring/ring-mock "0.2.0"]]

test/lambdacd_artifacts/sample_pipeline.clj

@@ -17,10 +17,12 @@
   (git/with-git "git@github.com:flosell/lambdacd-artifacts" steps))
 
 (defn produce-output [args ctx]
-  (shell/bash ctx (:cwd args) "lein test2junit"))
+  (shell/bash ctx (:cwd args)
+              "lein test2junit"
+              "exit 1"))
 
 (defn some-build-step [args ctx]
-    (step-support/chaining args ctx
+    (step-support/always-chaining args ctx
       (produce-output injected-args injected-ctx)
       (artifacts/publish-artifacts injected-args injected-ctx
                                    (:cwd injected-args) [#"test2junit/.*"