-
Notifications
You must be signed in to change notification settings - Fork 163
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
ci: running buildkite builds locally #3286
Comments
From my research, as long as we do not try to push images somewhere but use the local registry, it should be easy.
|
With the new pipeline we are closer to run it locally. Steps involved: |
lukedirtwalker
added a commit
that referenced
this issue
Jan 9, 2020
Running the new pipeline locally is not yet fully supported. The steps required currently are: * install [bk](https://github.com/buildkite/cli) * install [buildkite-agent](https://github.com/buildkite/agent) * `.builkite/pipeline2.sh > full-pipeline.yml` * `bk local run --env LOGNAME=$USER full-pipeline.yml` More information about local running: #3286 Fixes #3574 Fixes #3568
karampok
added a commit
that referenced
this issue
Jan 9, 2020
This PR adds timestamps in bazel and hardcodes the test-artifact folder in order to enable local run. Now everything runs locally apart from acceptance test that require some sudo interactive action. Contributes #3286
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During development, it would be great to be able to run a ci pipeline locally.
What does it :
bk run /path/to/pipeline.yml
as documentedwhere the pipeline.yaml to be the default pipeline (e.g. unit-tests) and the acceptance pipeline.
The text was updated successfully, but these errors were encountered: