Setup CI server. #100
Comments
|
The bazelbuild org has a CI instance that we are planning to use. That is currently undergoing an upgrade, and expected ETA within the next couple of weeks. |
|
I should also note, pull requests are welcome here to get this done. All that needs to be done is to follow instructions at bazelbuild/continuous-integration, and post a pull request to that repository |
|
according to documentation repo owners should allow access to robots in order for that CI to work. Could someone please do that? I'll see if I can find some time to send a PR to add buildfarm repo there. |
Since bazel-buildfarm setup is simple, default config works great for it. Fixes bazelbuild/bazel-buildfarm#100
|
https://github.com/orgs/bazelbuild/teams/robot (already) has write access to bazel-buildfarm, should be good to go for integration. |
|
thanks for checking, @werkt! Hopefully PR will be merged soon. |
|
buildfarm is on our brand new buildkite CI now. I think this can be closed? |
|
@buchgr, this issue was created mainly to track external contributor experience, which currently does not exist. For every PR there should be a signal about build and test results. |
|
For all pull requests and pushes from here on out, we have added feedback
from build kite, the solution that Jacob indicated, in the same section
where the CLA verification took place. You can see the progress of each
build on the supported platforms, ubuntu 14.04 , and 16.04, as well as the
build and test information distinctly. There are also links to summaries
about the test executions
That mostly meets my requirements for this issue, including the provision
for external contributor feedback, do you have anything else?
…On Feb 22, 2018 5:21 PM, "Taras Tsugrii" ***@***.***> wrote:
@buchgr <https://github.com/buchgr>, this issue was created mainly to
track external contributor experience, which currently does not exist. For
every PR there should be a signal about build and test results.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#100 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABTli8ASVVW393Eu-aEXJEbtAI4eylbks5tXehMgaJpZM4SKJvT>
.
|
|
Also he enabled a build badge, it is currently passing on the readme, it is
very cute, and I hope it never changes color from green to red
…On Feb 22, 2018 5:32 PM, "George Gensure" ***@***.***> wrote:
For all pull requests and pushes from here on out, we have added feedback
from build kite, the solution that Jacob indicated, in the same section
where the CLA verification took place. You can see the progress of each
build on the supported platforms, ubuntu 14.04 , 14.06, as well as the
build and test information distinctly. There are also links to summaries
about the test executions
That mostly meets my requirements for this issue, including the provision
for external contributor feedback, do you have anything else?
On Feb 22, 2018 5:21 PM, "Taras Tsugrii" ***@***.***> wrote:
> @buchgr <https://github.com/buchgr>, this issue was created mainly to
> track external contributor experience, which currently does not exist. For
> every PR there should be a signal about build and test results.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#100 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABTli8ASVVW393Eu-aEXJEbtAI4eylbks5tXehMgaJpZM4SKJvT>
> .
>
|
|
oh, sorry, the commit summaries with CI configs were somewhat scare in terms of description, so I didn't realize that they seem to be covering all use cases :) Also, when I clicked on a badge icon, I was greeted with request to create an account, so I'm not sure if everyone can access build results :( |
|
Doesn't seem like there's any facility for making that link content public, at a minimum we could repoint the markup content... |
|
Going to call this one closed in spirit, the CI is up and has been working for some time. |
It would be great if there was a Travis CI or Circle CI configured for PRs, so that reviewers can immediately see build and test results.
The text was updated successfully, but these errors were encountered: