-
Notifications
You must be signed in to change notification settings - Fork 8
Bazel Build Event Protocol (BEP) → bktec upload
#282
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
base: bktec-upload
Are you sure you want to change the base?
Conversation
PublishBuildToolEventStream is copied verbatim from bb-portal, and BuildEventHandler and BuildEventChannel interfaces/structs are created to be compatible with that code. This also resolves a bug in the earlier WIP implementation where most event sequence IDs were not acknowledged, resulting in a warning shown on the Bazel side sending the events.
| *.dll | ||
| *.so | ||
| *.dylib | ||
| /bktec |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
| logErrorAndExit(16, "upload: %v", err) | ||
| } | ||
| os.Exit(0) | ||
| } else if flag.Arg(0) == "bazel" && flag.Arg(1) == "listen" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[nit] I reckon switch will be more readable now we are most likely going to have many sub-commands.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would that be a nested switch?
switch flag.Arg(0) {
case "upload":
…
case "bazel":
switch {
case "listen":
…
default:
…
}
default:
…
}I figured it's simpler to use a flatter if for the moment, and think about whether we want to adopt a bells-and-whistles subcommand/flags package or use some nested switch etc.
Draft, based on #278 which is based on #277
Listen to Build Event Protocol (BEP) / Build Event Service (BES) and upload the XML test result files to Test Engine.
Related:
bktec upload: upload test results to Test Engine #278