-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Centralize building of Vector in one step on GH actions #2225
Comments
@a-rodin @MOZGIII I've assigned both of you to this because it overlaps with both the "Move to Github Actions" project and the "Kubernetes Integration" project. Both need to build Vector for tests, so it would be nice if they could use the same binary. I'm not sure if this is possible, but I wanted to include it in #2222. |
Ideally, we want to have a tree-like pipeline, with the step at the root that builds the binaries, and the following steps that run them. I'm thinking about a flow like this:
While the "build" and the steps that run afterwards are possible to automate within a single docker-compose container run with a shared file system, it's not going to work for test harness invocation. We can still build a |
Currently, we build Vector as part of testing Kubernetes, and we have plans to move all of our test to GH actions. It would be nice if we could build Vector once for all of our tests. Or, centralize building as much as possible. Building Vector takes a considerable amount of time and resources, so minimizing this is to our advantage.
The text was updated successfully, but these errors were encountered: