[MXNET-1191] Maven Jenkins Pipeline with Static Binary and GPU

[zachgk]

Description

This PR is the third and final part of the maven Jenkins publishing that adds integration with the static building scripts placed in tools as well as enabling GPU.

Note that this PR depends on (and is based on top of until they are merged) #13450 and #13707. The changes as part of this PR are only those located in a3c7d46.

Please review so the pipeline can be put into production:
@nswamy @lanking520 @andrewfayres @piyushghai @marcoabreu @yzhliu @szha

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:
• Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
• Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
• Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
• Code is well-documented:
• For user-facing API changes, API doc string has been updated.
• For new C++ functions in header files, their functionalities and arguments are documented.
• For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
• Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
• To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

[Roshrini]

@mxnet-label-bot Add [pr-awaiting-review]

[zachgk]

@mxnet-label-bot add [CI, Java, Maven, Scala]

[lanking520]

Please do a rebase with master

[piyushghai]

Curious, why add the boolean OR true condition here ?

[zachgk]

The "|| true" means that the line will always evaluate with a zero exit code. For scripts with "set -e", any line evaluating with a nonzero exit code will exit the script. I am not sure why we ignore problems on the update, but this is done throughout the CI install scripts.

[piyushghai]

Super! Thanks.

[marcoabreu]

Sometimes, some apt repositories are not available and apt-get update fails. If that's the case, we still want to go ahead since all other repositories still updated (think of 1 out of 500 repositories not being available). If the repository we actually need for the installation is actually not available, the install will fail properly and that's fine. But in most cases, it's just an unused and unrelated repository that's not available and thus we just ignore it.

[marcoabreu]

a3c7d46 LGTM

[lanking520]

Ran it for a couple of times on my local computer and it is working just fine. Also see @zachgk tested a couple of times on Jenkins, overall looks good.