-
Notifications
You must be signed in to change notification settings - Fork 243
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
feat(extraction): support tree artifacts in bazel extractor #4932
feat(extraction): support tree artifacts in bazel extractor #4932
Conversation
/gcbrun |
It looks like the go-module build fails as well as gofmt checks. |
What is go-module build? I don't think I have access to the build logs so no idea why it failed or how to run it locally. With gofmt should be a bit easier. |
Ah, we want the Go code to be buildable outside of bazel so also run: |
43f1240
to
e0405fd
Compare
I updated this PR. Should be good now. @shahms can you trigger presubmits again? |
/gcbrun |
3cf6bf7
to
fecc5e1
Compare
/gcbrun |
fecc5e1
to
1fc1c3b
Compare
Usually artifacts in bazel are regular files. But sometimes it can be directories (tree artifacts): https://docs.bazel.build/versions/master/glossary.html#artifact In this case extractor has to recursively include all files in such directories. Had to refactor unit test as now extractor performs file IO so need to initialize all input files by creating empty files.
1fc1c3b
to
ade83a3
Compare
/gcbrun |
/gcbrun |
/gcbrun |
Usually artifacts in bazel are regular files. But sometimes it can be directories
(tree artifacts): https://docs.bazel.build/versions/master/glossary.html#artifact
In this case extractor has to recursively include all files in such directories.
Had to refactor unit test as now extractor performs file IO so need to initialize
all input files by creating empty files.