Skip to content

Buildkite Pipeline - Add other relevant pipeline steps #2

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.

Sign up for GitHub

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

Jump to bottom
Open
thundergolfer opened this issue May 19, 2019 · 0 comments
Open

Buildkite Pipeline - Add other relevant pipeline steps #2

thundergolfer opened this issue May 19, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@thundergolfer
Copy link
Owner

Description

Running bazel test //... is great and all, but there are other CI steps that any respectable Bazel monorepo should run. Right now I can think of:

  1. BUILD file and other Bazel file linting. Important in context of project
  2. Code linting (this could be costly if this project involves 4-5 different languages)
  3. Some sort of WORKSPACE file validation
@thundergolfer thundergolfer added the enhancement New feature or request label May 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@thundergolfer