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

Remove redundant prow jobs covered by golangci-lint #661

Merged

Conversation

lentzi90
Copy link
Member

@lentzi90 lentzi90 commented Mar 5, 2024

BMO:

  • Remove gofmt for main and release-0.5. They have GitHub actions that
    run golangci-lint and includes gofmt.
  • Older release branches do not have the GitHub action so they are left
    as is.
  • Remove golint for main and release-0.5 as we have GitHub actions for
    them.
  • Add test jobs for verifying that the scripts and make targets work.

CAPM3:

  • Remove gofmt, govet and gosec. They are all part of golangci-lint for all
    tested branches. Release-1.4 has a prow job, the rest have GitHub
    actions.

IPAM:

  • Remove gosec, gofmt and govet. They are all part of golangci-lint for
    all tested branches. Release-1.4 has a prow job, the rest have GitHub
    actions.

Please check carefully!
/hold

@metal3-io-bot metal3-io-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 5, 2024
@tuminoid
Copy link
Member

tuminoid commented Mar 5, 2024

/cc @kashifest
to check this, golangci is mostly his work.

@metal3-io-bot metal3-io-bot requested a review from kashifest March 5, 2024 14:05
prow/manifests/overlays/metal3/config.yaml Show resolved Hide resolved
prow/manifests/overlays/metal3/config.yaml Show resolved Hide resolved
prow/manifests/overlays/metal3/config.yaml Show resolved Hide resolved
prow/manifests/overlays/metal3/config.yaml Outdated Show resolved Hide resolved
prow/manifests/overlays/metal3/config.yaml Outdated Show resolved Hide resolved
@tuminoid
Copy link
Member

tuminoid commented Mar 6, 2024

@tuminoid for some reason I dont see the workflow file in 0.5 branch either, are you sure the golangci-lint action is active on that branch ? IMO we should only remove from main branch.

OK, the workflow file isn't there as I expected. Then only main can be removed, or we can add the workflow file in 0.5?

@kashifest
Copy link
Member

@tuminoid for some reason I dont see the workflow file in 0.5 branch either, are you sure the golangci-lint action is active on that branch ? IMO we should only remove from main branch.

OK, the workflow file isn't there as I expected. Then only main can be removed, or we can add the workflow file in 0.5?

Yes, I will add it

@lentzi90 lentzi90 force-pushed the lentzi90/remove-redundant-prow-jobs branch from 0b18deb to 02fe381 Compare March 6, 2024 08:01
@lentzi90
Copy link
Member Author

lentzi90 commented Mar 6, 2024

@tuminoid for some reason I dont see the workflow file in 0.5 branch either, are you sure the golangci-lint action is active on that branch ? IMO we should only remove from main branch.

OK, the workflow file isn't there as I expected. Then only main can be removed, or we can add the workflow file in 0.5?

Yes, I will add it

Thanks! Then I will remove gofmt from main and release-0.5 here and we can merge after the action is added in 0.5. I noticed also that we have a redundant golint for BMO main. I will remove that as well.

BMO:

- Remove gofmt for main and release-0.5. They have GitHub actions that
  run golangci-lint and includes gofmt.
- Older release branches do not have the GitHub action so they are left
  as is.
- Remove golint for main and release-0.5 as we have GitHub actions for
  them.
- Add test jobs for verifying that the scripts and make targets work.

CAPM3:

- Remove gofmt, govet and gosec. They are all part of golangci-lint for all
  tested branches. Release-1.4 has a prow job, the rest have GitHub
  actions.

IPAM:

- Remove gosec, gofmt and govet. They are all part of golangci-lint for
  all tested branches. Release-1.4 has a prow job, the rest have GitHub
  actions.

Signed-off-by: Lennart Jern <lennart.jern@est.tech>
@tuminoid
Copy link
Member

tuminoid commented Mar 6, 2024

Thanks! Then I will remove gofmt from main and release-0.5 here and we can merge after the action is added in 0.5. I noticed also that we have a redundant golint for BMO main. I will remove that as well.

Follow-up with removal of the hack scripts and Makefile targets in each repo as well as they are removed from here to remove the cruft to maintain for no value.

@lentzi90 lentzi90 force-pushed the lentzi90/remove-redundant-prow-jobs branch from 02fe381 to 8bd17bc Compare March 6, 2024 08:40
@lentzi90
Copy link
Member Author

lentzi90 commented Mar 6, 2024

Follow-up with removal of the hack scripts and Makefile targets in each repo as well as they are removed from here to remove the cruft to maintain for no value.

I have added these as tasks for the contrib-fest 😄

@lentzi90
Copy link
Member Author

lentzi90 commented Mar 8, 2024

/override test-ubuntu-integration-main

@metal3-io-bot
Copy link
Collaborator

@lentzi90: Overrode contexts on behalf of lentzi90: test-ubuntu-integration-main

In response to this:

/override test-ubuntu-integration-main

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/test-infra repository.

@kashifest
Copy link
Member

/approve

@metal3-io-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kashifest

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 Mar 8, 2024
@lentzi90
Copy link
Member Author

lentzi90 commented Mar 8, 2024

/hold cancel
/cc @tuminoid

@metal3-io-bot metal3-io-bot requested a review from tuminoid March 8, 2024 10:51
@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 Mar 8, 2024
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 Mar 8, 2024
@metal3-io-bot metal3-io-bot merged commit 4f4acb9 into metal3-io:main Mar 8, 2024
6 checks passed
@metal3-io-bot
Copy link
Collaborator

@lentzi90: Updated the config configmap in namespace prow at cluster default using the following files:

  • key config.yaml using file prow/manifests/overlays/metal3/config.yaml

In response to this:

BMO:

  • Remove gofmt for main and release-0.5. They have GitHub actions that
    run golangci-lint and includes gofmt.
  • Older release branches do not have the GitHub action so they are left
    as is.
  • Remove golint for main and release-0.5 as we have GitHub actions for
    them.
  • Add test jobs for verifying that the scripts and make targets work.

CAPM3:

  • Remove gofmt, govet and gosec. They are all part of golangci-lint for all
    tested branches. Release-1.4 has a prow job, the rest have GitHub
    actions.

IPAM:

  • Remove gosec, gofmt and govet. They are all part of golangci-lint for
    all tested branches. Release-1.4 has a prow job, the rest have GitHub
    actions.

Please check carefully!
/hold

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/test-infra repository.

@lentzi90 lentzi90 deleted the lentzi90/remove-redundant-prow-jobs branch March 8, 2024 11:33
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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants