[WIP] Run Bazel build/tests as part of Travis CI

[neuromage]

This change is 

[yebrahim]

Thanks for doing this @neuromage!
Is it faster to install the bazel debian package rather than use the install script? (e.g. how it's done in https://github.com/korfuri/bazel-travis)

[neuromage]

I don't know if it's faster tbh. But this is how Bazel itself does it for their go rules:
https://github.com/bazelbuild/rules_go/blob/master/.travis.yml

[yebrahim]

Should we remove the lines 49-61?

[neuromage]

Did you mean 59 - 61? I think we should keep it, as long as want go build / go test to continue to work. Also, it's still what we use to release/build images.

[yebrahim]

Can you add a note what we're using bazel for then? I thought we were going to switch everything to bazel. I'd love to keep using go build/test wherever we can because they're much faster, but I also think it's good to be consistent with the build system.

[neuromage]

This prevents the problem of #638 where the bazel build is broken at HEAD. Bazel is needed especially when the proto definitions change.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: neuromage
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: paveldournov

If they are not already assigned, you can assign the PR to them by writing /assign @paveldournov in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: neuromage
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: paveldournov

If they are not already assigned, you can assign the PR to them by writing /assign @paveldournov in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[neuromage]

/retest

[k8s-ci-robot]

@neuromage: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
kubeflow-pipeline-sample-test	ae188df	link	/test kubeflow-pipeline-sample-test
kubeflow-pipeline-upgrade-test	ae188df	link	/test kubeflow-pipeline-upgrade-test

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.