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 not needed anymore Prow jobs #9771

Open
3 of 43 tasks
Sawthis opened this issue Jan 25, 2024 · 2 comments
Open
3 of 43 tasks

Remove not needed anymore Prow jobs #9771

Sawthis opened this issue Jan 25, 2024 · 2 comments
Labels
area/ci Issues or PRs related to CI related topics Epic

Comments

@Sawthis
Copy link
Contributor

Sawthis commented Jan 25, 2024

Description

A lot of jobs are generated for each repository defined in the templates/config.yaml

  • validate-dockerfiles(hadolint) - Should be migrated to Github actions.
  • checkconfig(Validate inrepo prow configs) - Do we need it? I think noone is using InRepo Prow configs.
  • pjconfigtest(Run ginkgo suite tests for prowjobs definitions) - Do we need it for other repositories than test-infra?
  • pjtester(Schedule prowjobs tests using pjtester) - Won't be needed after migration outside of Prow.
  • vpathguard(Run pjtester vpathguard) - Won't be needed after migration outside of Prow.
  • presubmit-scanner(Run Gitleaks presubmit scanner to detect commited sensitive data) - Should we migrate it to GH actions and each team should use it?

80 Prow jobs owned by us:

Can be deleted after last Kyma release planned for end of February.

  • pre-release-pr-image-guard
  • pre-main-kyma-validate-image-definitions
  • pre-main-kyma-validate-image-existence
  • pre-main-kyma-validate-dockerfiles
  • pull-kyma-checkconfig
  • pull-kyma-pjconfigtest
  • pull-kyma-pjtester
  • pull-kyma-vpathguard
  • post-kyma-release-cluster
  • kyma-whitesource-scan
  • hydroform-whitesource-scan
  • reconciler-whitesource-scan
  • kyma-2.20-whitesource-scan
  • kyma-2.19-whitesource-scan

Should be migrated to the GH actions together with image builder.

  • post-main-build-testimages
  • post-test-infra-ko-build

Blocked with migration of KCP to the new security scans solution.

  • control-plane-whitesource-scan

Won't be needed after migration outside of Prow.

  • pull-k8s-prow-integration
  • ci-prow-autobump
  • ci-prow-autobump-jobs
  • post-test-infra-deploy-prow
  • pull-test-infra-checkconfig
  • pull-test-infra-pjconfigtest
  • pull-test-infra-pjtester
  • pull-test-infra-vpathguard
  • pre-main-test-infra-validate-generated-files
  • pull-k8s-prow-unit-test
  • ci-k8s-prow-sync-upstream
  • ci-k8s-prow-publish-tag
  • ci-k8s-prow-autobump-testimages
  • post-k8s-prow-build-release
  • post-gencred-refresh-kubeconfigs
    • Refresh kubeconfigs for workload clusters after config change, to be removed with prow
  • ci-gencred-refresh-kubeconfigs
    • Refresh kubeconfigs for workload clusters after config change, to be removed with prow
  • pull-slack-bot-checkconfig
    • validation of prowjobs in slack-bot repository, to be removed with prow
  • gcloud-ssh-keys-cleaner
    • cleans os-login ssh keys on gcp project, not needed after prow and workloads project deletion
  • orphaned-disks-cleaner
    • cleans orphaned disks on gcp project, not needed after prow and workloads project deletion
  • orphaned-ips-cleaner
    • cleans orphaned ips on gcp project, not needed after prow and workloads project deletion
  • orphaned-clusters-cleaner
    • cleans orphaned clusters on gcp project, not needed after prow and workloads project deletion
  • orphaned-vms-cleaner
    • cleans orphaned vms on gcp project, not needed after prow and workloads project deletion
  • orphaned-loadbalancer-cleaner
    • cleans orphaned lbs on gcp project, not needed after prow and workloads project deletion
  • orphaned-dns-cleaner
    • cleans orphaned dns on gcp project, probably not needed after prow and workloads project deletion

Reasons

Acceptance Criteria

  • All Prow jobs mentioned in this issue are migrated to Github actions.
  • All Prow jobs mentioned in this issue are removed.

Attachments

#9470

@Sawthis Sawthis added Epic area/ci Issues or PRs related to CI related topics labels Jan 25, 2024
Copy link

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 26, 2024
Copy link

github-actions bot commented Apr 2, 2024

This issue has been automatically closed due to the lack of recent activity.
/lifecycle rotten

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
@kyma-bot kyma-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 2, 2024
@Sawthis Sawthis removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Apr 10, 2024
@Sawthis Sawthis reopened this Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Issues or PRs related to CI related topics Epic
Projects
None yet
Development

No branches or pull requests

2 participants