-
Notifications
You must be signed in to change notification settings - Fork 23
🌱 Add FKAS build to PR checks #1102
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: main
Are you sure you want to change the base?
🌱 Add FKAS build to PR checks #1102
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
value: "TRUE" | ||
image: docker.io/golang:1.24 | ||
imagePullPolicy: Always | ||
- name: build-fkas |
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.
As mentioed offline, this docker build is not actually building versus CAPM3 branch head, but static version of CAPM3.
- name: build-fkas | ||
branches: | ||
- release-1.10 | ||
run_if_changed: "^hack/fake-apiserver/.*$" |
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.
This also needs to run if CAPM3 api or baremetal is changed.
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.
Same fix is needed for all the release branches and main.
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.
Yup! I accidentally pushed before I had the change saved on all files. I only added the api/
because I changed the fkas so that it doesn't use capm3 baremetal/
.
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.
How about main? That is missing here.
dafcb95
to
45a555f
Compare
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.
1.9 is tested only, does FKAS building work there? We don't want to be submitting fixes there for this.
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.
Thinking this through in more detail, I realized: hack/build.sh
calls make build-fkas
but the build-fkas
is only added to the Makefile in main branch. So this job is not actually doing anything in any of the release branches....
Questions is do we want to add fkas build check in the release brances? If yes should the fkas keep using the static CAPM3 version of should it use new dynamic style?. I can open the PRs once I know if the fkas-build should use static or dynamic CAPM3 in the existing releases
Signed-off-by: peppi-lotta <[email protected]>
45a555f
to
81888b4
Compare
Add FKAS build to PR checks runs when something changes under
./hack/fake-apiserver
file.Related PR: metal3-io/cluster-api-provider-metal3#2814