-
Notifications
You must be signed in to change notification settings - Fork 192
use build tooling for building capabilities component #4307
use build tooling for building capabilities component #4307
Conversation
8cc0471
to
0f72d1d
Compare
Cluster Generation A/B Results: |
Codecov Report
@@ Coverage Diff @@
## feature/runtime-core #4307 +/- ##
========================================================
- Coverage 49.60% 48.72% -0.88%
========================================================
Files 452 482 +30
Lines 45044 47175 +2131
========================================================
+ Hits 22344 22987 +643
- Misses 20577 22015 +1438
- Partials 2123 2173 +50
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
781f052
to
dcba2d1
Compare
Cluster Generation A/B Results: |
dcba2d1
to
377abdf
Compare
Cluster Generation A/B Results: |
377abdf
to
e9348e9
Compare
Cluster Generation A/B Results: |
CAPD integration tests have been consistently failing for some reason, it looks unrelated to the changes in this pr |
@@ -0,0 +1,75 @@ | |||
# Copyright 2023 VMware, Inc. All Rights Reserved. |
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.
Suggestion: Purely from user experience perspective, is it possible to rename this Dockerfile to be something else from which people understand this Dockerfile cannot be directly used by docker build
under T-F root. (Or we could add some inline comments?)
The reason why I am raising this is because I got confused at the beginning until I looked into the dockerfile content.
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.
docker-build
make target in t-f Makefile calls the docker-build
target command in each component's Makefile, but I can add a comment to provide more clarity
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.
added the comment
@@ -0,0 +1,297 @@ | |||
.DEFAULT_GOAL := help |
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.
question: when we make changes in https://github.com/vmware-tanzu/build-tooling-for-integrations/tree/main/templates, or when user makes changes against this file in T-F by adding more components, what we can do to make things consistent ?
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.
it's up to the consumer(t-f) on when they want to consume the new release from https://github.com/vmware-tanzu/build-tooling-for-integrations, but when they update the Makefile in t-f it is their responsibility to update the components var, but this will change later when the design gets approved and implemented(we will have a config file to maintain components)
e9348e9
to
d5385d2
Compare
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
.github/workflows/build-using-buildtooling-for-pullrequests.yaml
Outdated
Show resolved
Hide resolved
IMG_VERSION_OVERRIDE ?= $(IMG_DEFAULT_TAG) | ||
GOPROXY ?= "https://proxy.golang.org,direct" | ||
PLATFORM=local | ||
COMPONENTS ?= capabilities/client capabilities/controller.capabilities-controller-manager.capabilities |
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.
Could you add a comment about what this line means and how COMPONENTS
is supposed to be used?
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.
added a comment that provides link to the documentation
Cluster Generation A/B Results: |
9ee961e
to
5abfcaa
Compare
What this PR does / why we need it
This pr uses build tooling for building capabilities component
Which issue(s) this PR fixes
Fixes #4414
Describe testing done for PR
Ran
make docker-build-all -f build-tooling.mk
from the project's root directory and verified that the capabilities component is built.Release note
Additional information
Special notes for your reviewer