Skip to content

Conversation

peppi-lotta
Copy link
Member

Add FKAS build to PR checks runs when something changes under ./hack/fake-apiserver file.
Related PR: metal3-io/cluster-api-provider-metal3#2814

@metal3-io-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lentzi90 for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@metal3-io-bot metal3-io-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 19, 2025
value: "TRUE"
image: docker.io/golang:1.24
imagePullPolicy: Always
- name: build-fkas
Copy link
Member

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/.*$"
Copy link
Member

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.

Copy link
Member

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.

Copy link
Member Author

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/.

Copy link
Member

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.

@peppi-lotta peppi-lotta force-pushed the peppi-lotta/add-fkas-build-pr-check branch 3 times, most recently from dafcb95 to 45a555f Compare October 3, 2025 07:19
Copy link
Member

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.

Copy link
Member Author

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]>
@peppi-lotta peppi-lotta force-pushed the peppi-lotta/add-fkas-build-pr-check branch from 45a555f to 81888b4 Compare October 6, 2025 10:58
@metal3-io-bot metal3-io-bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants