[maven-jenkins-lib] branch master updated: maven-invoker keeps lock on jar (under investigation), so can't fully clean up the workspace. No reason to fail the build.

[rf...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

rfscholte pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git


The following commit(s) were added to refs/heads/master by this push:
     new 5d5c1c3  maven-invoker keeps lock on jar (under investigation), so can't fully clean up the workspace. No reason to fail the build.
5d5c1c3 is described below

commit 5d5c1c38117363789390a376a0c0f02226296ce7
Author: rfscholte <rf...@apache.org>
AuthorDate: Sat Apr 6 14:21:52 2019 +0200

    maven-invoker keeps lock on jar (under investigation), so can't fully clean up the workspace. No reason to fail the build.
---
 vars/asfMavenTlpStdBuild.groovy | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/vars/asfMavenTlpStdBuild.groovy b/vars/asfMavenTlpStdBuild.groovy
index 6f14524..8bf4492 100644
--- a/vars/asfMavenTlpStdBuild.groovy
+++ b/vars/asfMavenTlpStdBuild.groovy
@@ -135,7 +135,11 @@ def call(Map params = [:]) {
                   echo "[FAIL FAST] ${failingFast} had first failure, ignoring ${e.message}"
                 }
               } finally {
-                cleanWs()
+			    try {
+                  cleanWs()
+				} catch(IOException e) {
+				  echo "Failed to clean up workspace: ${e}"
+				}
               }
             }
           }