From a9c46cc206ead5295560fbd2a0959925809b6a6d Mon Sep 17 00:00:00 2001
From: giventocode <3589801+giventocode@users.noreply.github.com>
Date: Tue, 25 Feb 2020 18:03:08 -0500
Subject: [PATCH]  - added condition to sample pipelines  - added more info in
 timeout value.

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index f0d6c29..e69fb39 100644
--- a/README.md
+++ b/README.md
@@ -274,7 +274,7 @@ POSITIONAL ARGUMENTS
 
 ```  bash
 FLAGS
-    --timeout              Execution timeout. Default 120s
+    --timeout              Execution timeout in seconds. Integer value. Default is 120
     --junit_report         Create a JUnit XML report from the test results.
     --tags_report          Create a CSV report from the test results that includes the test cases tags.
     --max_parallel_tests   Sets the level of parallelism for test notebook execution.
@@ -344,6 +344,7 @@ steps:
     testResultsFormat: 'JUnit'
     testResultsFiles: '**/test-*.xml'
     testRunTitle: 'Publish Nutter results'
+  condition: succeededOrFailed()
 ```
 
 In some scenarios, the notebooks under tests must be executed in a  pre-configured test workspace, other than the development one, that contains the necessary pre-requisites such as test data, tables or mounted points. In such scenarios, you can use the pipeline to deploy the notebooks to the test workspace before executing the tests with Nutter.
@@ -394,6 +395,7 @@ steps:
     testResultsFormat: 'JUnit'
     testResultsFiles: '**/test-*.xml'
     testRunTitle: 'Publish Nutter results'
+  condition: succeededOrFailed()
 ```
 
 ## Contributing