Heya, It looks like our GitHub PR build automation was sensitive to the download URL used for fetching the Yetus release. Yetus recently released 0.15.1, and so the 0.15.0 (that we rely upon) was moved out of the downloads server and into the archives. We actually have a script for dealing with this gracefully that we use in nightlies, just not in PRs. I've fixed this specific problem via HBASE-29163. Note that there's still some weirdness affecting branch-2 release lines, but PRs are at least running again.
If you have any open PRs with changes posted since the Yetus release went out, you'll need to rebase onto or merge the latest upstream ref into your PR branch in order to get the fix. Do holler if you have any questions or see further issues, I'll see what I can do. Good luck and happy HBaseing. Nick
