[
https://issues.apache.org/jira/browse/SLING-8572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16928409#comment-16928409
]
Robert Munteanu commented on SLING-8572:
----------------------------------------
I've expanded the status check to use {{currentBuild.currentResult}} (variant
2 in debug output ). For the sling whiteboard the output is
* successful build: {{[DEBUG] current result (variant 1) is SUCCESS, current
result (variant 2) is SUCCESS, previous result is SUCCESS}}
* failed build: {{[DEBUG] current result (variant 1) is FAILURE, current result
(variant 2) is FAILURE, previous result is SUCCESS}}
For the IDE tooling:
* successful build: {{[DEBUG] current result (variant 1) is null, current
result (variant 2) is SUCCESS, previous result is SUCCESS}}
* failed build: {{[DEBUG] current result (variant 1) is FAILURE, current result
(variant 2) is FAILURE, previous result is SUCCESS}}
The fix seems to be to use {{curentBuild.currentResult}} instead of
{{currentBuild.result}}.
> sling-ide-tooling is reported as broken but is actually successful
> ------------------------------------------------------------------
>
> Key: SLING-8572
> URL: https://issues.apache.org/jira/browse/SLING-8572
> Project: Sling
> Issue Type: Bug
> Components: Build and Source Control, IDE
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
>
> https://builds.apache.org/job/Sling/job/sling-ide-tooling/job/master/46/ was
> successful, but the notification said that it was broken
> {noformat}
> [Pipeline] { (Notifications)
> [Pipeline] echo
> Status change is BROKEN, notifications will be sent.
> [Pipeline] emailext
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
