[
https://issues.apache.org/jira/browse/HBASE-20638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489250#comment-16489250
]
Sean Busbey commented on HBASE-20638:
-------------------------------------
oh thought of one other thing. if we track in a variable and then exit after
the block, once we add the tests from HBASE-20334 it'll need to look like:
{code}
status="0"
if some_command ; then
echo "success!"
else
echo "failure!"
status="1"
fi
if [ "$status" -ne 0 ] ; then
exit "${status}"
fi
# other stuff
{code}
since we can't continue if there's a failure. so it'll be a bit over-engineered
unless we add in other things that might fail between the script that generates
the artifact and the stuff that'll need to use it.
> nightly source artifact testing should fail the stage if it's going to report
> an error on jira
> ----------------------------------------------------------------------------------------------
>
> Key: HBASE-20638
> URL: https://issues.apache.org/jira/browse/HBASE-20638
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Major
> Attachments: HBASE-20638.0.patch
>
>
> Looks like the source artifact testing is properly reporting failures on
> jira, but is marking the stage on jenkins as successful. that makes it much
> hard to track over time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
