Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Bazel CI failures clearer #807

Merged
merged 2 commits into from
Nov 14, 2018
Merged

Conversation

drigz
Copy link
Contributor

@drigz drigz commented Nov 14, 2018

  • don't try to run tests if the BUILD files are out-of-date
  • run buildifier even if the tests fail, as it may still be useful
  • use a parameter to hold Bazel config to simplify config.yml
  • use default output_base (hopefully it works, this is because it's hard
    to have nested envvars with CircleCL)
  • ignore the vendor/ directory when running Gazelle
    (otherwise it will fail if you've used dep to create vendor/)

@drigz
Copy link
Contributor Author

drigz commented Nov 14, 2018

Don't mind me, just trying to get the CI config valid.

- don't try to run tests if the BUILD files are out-of-date
- run buildifier even if the tests fail, as it may still be useful
- use a parameter to hold Bazel config to simplify config.yml
- ignore the vendor/ directory when running Gazelle
  (otherwise it will fail if you've used `dep` to create vendor/)
@codecov-io
Copy link

codecov-io commented Nov 14, 2018

Codecov Report

Merging #807 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##           master    #807   +/-   ##
======================================
  Coverage    53.3%   53.3%           
======================================
  Files          30      30           
  Lines        3371    3371           
======================================
  Hits         1797    1797           
  Misses       1399    1399           
  Partials      175     175

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7c0cd0...7239462. Read the comment docs.

@drigz
Copy link
Contributor Author

drigz commented Nov 14, 2018

@achew22 Could you review this? Hopefully it'll help avoid confusion like in #806.

@achew22 achew22 merged commit 73373e5 into grpc-ecosystem:master Nov 14, 2018
adasari pushed a commit to adasari/grpc-gateway that referenced this pull request Apr 9, 2020
* Make Bazel CI failures clearer

- don't try to run tests if the BUILD files are out-of-date
- run buildifier even if the tests fail, as it may still be useful
- use a parameter to hold Bazel config to simplify config.yml
- ignore the vendor/ directory when running Gazelle
  (otherwise it will fail if you've used `dep` to create vendor/)

* Add Bazel invocation to CONTRIBUTING.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants