Skip to content
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

🌱 Add scalability test prow triggers #953

Merged

Conversation

mquhuy
Copy link
Member

@mquhuy mquhuy commented Jan 15, 2025

This commit adds the new scalability tests to prow

@metal3-io-bot metal3-io-bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jan 15, 2025
@mquhuy
Copy link
Member Author

mquhuy commented Jan 15, 2025

/cc @lentzi90 @tuminoid @kashifest

Copy link
Member

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@metal3-io-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

The full list of commands accepted by this bot can be found here.

The pull request process is described 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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2025
Copy link
Member

@kashifest kashifest left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 15, 2025
@@ -200,3 +200,10 @@ presubmits:
agent: jenkins
always_run: false
optional: true
# name: metal3-centos-e2e-feature-test-release-1-9-scalability
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These comments do nothing :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Imo they're still useful as separation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In release branch config they seem removed altogether.

They're supposed to show the template format, like they do in main config.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/hold

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not something we have agreed on. We started adding those comments back when the prow config grows so big and unorganized, so the point of having them is just so that we can tell apart which from which, we didn't discussed the "rules" of where they should be and how they should look like/

Since you insist I'll remove these comments now, but IMO adding the comments here really help making the separation easier to follow.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Convention is form of agreement as well.

Zero information comments are worth nothing, they're actually worth negative since they need to be maintained not to be outdated.

If you want to use separator, use empty line.

@mquhuy
Copy link
Member Author

mquhuy commented Jan 15, 2025

/test metal3-ubuntu-e2e-integration-test-main

@metal3-io-bot metal3-io-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 15, 2025
@mquhuy
Copy link
Member Author

mquhuy commented Jan 15, 2025

/retest

1 similar comment
@mquhuy
Copy link
Member Author

mquhuy commented Jan 16, 2025

/retest

This commit adds the new scalability tests to prow

Signed-off-by: Huy Mai <huy.mai@est.tech>
@mquhuy mquhuy force-pushed the mquhuy/add-scalability-tests-to-prow branch from fd0e385 to 358e71a Compare January 16, 2025 13:07
@metal3-io-bot metal3-io-bot removed the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2025
@mquhuy
Copy link
Member Author

mquhuy commented Jan 16, 2025

/test metal3-ubuntu-e2e-integration-test-main

1 similar comment
@mquhuy
Copy link
Member Author

mquhuy commented Jan 16, 2025

/test metal3-ubuntu-e2e-integration-test-main

Copy link
Member

@tuminoid tuminoid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2025
@tuminoid
Copy link
Member

/unhold

@metal3-io-bot metal3-io-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 17, 2025
@metal3-io-bot metal3-io-bot merged commit 12b3384 into metal3-io:main Jan 17, 2025
4 of 5 checks passed
@metal3-io-bot metal3-io-bot deleted the mquhuy/add-scalability-tests-to-prow branch January 17, 2025 07:35
@metal3-io-bot
Copy link
Collaborator

@mquhuy: Updated the job-config configmap in namespace prow at cluster default using the following files:

  • key cluster-api-provider-metal3-release-1.9.yaml using file prow/config/jobs/metal3-io/cluster-api-provider-metal3-release-1.9.yaml
  • key cluster-api-provider-metal3.yaml using file prow/config/jobs/metal3-io/cluster-api-provider-metal3.yaml

In response to this:

This commit adds the new scalability tests to prow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. 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.

5 participants