linse/frappy
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Correctly publish pylint results

Browse Source 
Change-Id: Ica71417f8e13959eb46065f1fe664b362d701d8c
Reviewed-on: https://forge.frm2.tum.de/review/19619
Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de>
Reviewed-by: Bjoern Pedersen <bjoern.pedersen@frm2.tum.de>
This commit is contained in:
Björn Pedersen
2018-12-14 13:32:55 +01:00
committed by Bjoern Pedersen
parent c0f7034b30
commit 17ae9a4be6
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
ci/Jenkinsfile vendored
View File

@ -62,12 +62,13 @@ fi
} // credentials } // credentials
echo "pylint result: $res" echo "pylint result: $res"
this.verifyresult.put('pylint'+pyver, 1)
if ( res != 0 ) { if ( res != 0 ) {
currentBuild.result='FAILURE' currentBuild.result='FAILURE'
this.verifyresult.put('pylint'+ pyver, -1) this.verifyresult.put('pylint'+ pyver, -1)
status = 'FAILURE' status = 'FAILURE'
} }
gerritverificationpublisher([ gerritverificationpublisher([
verifyStatusValue: this.verifyresult['pylint'+pyver], verifyStatusValue: this.verifyresult['pylint'+pyver],
verifyStatusCategory: 'pylint ', verifyStatusCategory: 'pylint ',