This is an automated email from the ASF dual-hosted git repository. cdutz pushed a commit to branch develop in repository https://gitbox.apache.org/repos/asf/incubator-plc4x.git
The following commit(s) were added to refs/heads/develop by this push: new 4d7ff5a Commented the timeout back in again (Wasn't reducing the number of kills) .. I am assuming it's due to some OS limitation and usually occurs with parallel executed builds. 4d7ff5a is described below commit 4d7ff5a280d2c2345b85c350a95c182b9cfa6c26 Author: Christofer Dutz <christofer.d...@c-ware.de> AuthorDate: Wed Feb 6 14:05:38 2019 +0100 Commented the timeout back in again (Wasn't reducing the number of kills) .. I am assuming it's due to some OS limitation and usually occurs with parallel executed builds. --- Jenkinsfile | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/Jenkinsfile b/Jenkinsfile index 6cc4977..ff78e1a 100644 --- a/Jenkinsfile +++ b/Jenkinsfile @@ -36,7 +36,7 @@ pipeline { JENKINS_PROFILE = 'jenkins-build' // On non develop build we don't want to pollute the global m2 repo MVN_LOCAL_REPO_OPT = '-Dmaven.repo.local=.repository' - // Testfails will be handled by the jenkins junit steps and mark the build as unstable. + // Test failures will be handled by the jenkins junit steps and mark the build as unstable. MVN_TEST_FAIL_IGNORE = '-Dmaven.test.failure.ignore=true' } @@ -47,8 +47,7 @@ pipeline { options { // Kill this job after one hour. - // TODO: Disabled for finding out if this is what's randomly killing jobs ... - //timeout(time: 1, unit: 'HOURS') + timeout(time: 1, unit: 'HOURS') // When we have test-fails e.g. we don't need to run the remaining steps skipStagesAfterUnstable() buildDiscarder(logRotator(numToKeepStr: '5', artifactNumToKeepStr: '3'))