Skip to content

Remove all Prow configuration for retiring repositories - #960

Open
dprotaso wants to merge 2 commits into
mainfrom
dprotaso/remove-retired-release-jobs
Open

dprotaso wants to merge 2 commits into
mainfrom
dprotaso/remove-retired-release-jobs

Conversation

@dprotaso

@dprotaso dprotaso commented Nov 1, 2026 •

Copy link
Copy Markdown
Member

Summary

Remove all repository-specific Prow job configuration for repositories being archived in knative/community#1802:

  • autoscaler-keda
  • backstage-plugins
  • discovery
  • eventing-autoscaler-keda
  • kn-plugin-sample
  • kn-plugin-service-log
  • kn-plugin-source-kamelet
  • security-guard

Remove main-branch and release-branch job inputs and their generated outputs, including presubmits, continuous tests, nightly publishers, and release publishers. Regenerate TestGrid configuration to remove the associated dashboards, and remove stale autobump exclusions and the old test-infra fork's approve-plugin entry.

The remaining repositories marked ARCHIVE in the tracking issue already have no repository-specific jobs configured here. Historical documentation links and shared organization-wide Prow policies remain unchanged.

This updates the original release-only scope: main-branch CI is also removed, including Discovery and plugin-sample. Removing the job inputs prevents release-jobs-syncer from recreating their jobs.

This PR does not delete release artifacts, change Knative Operator integrations, or remove the separate knative/release or downstream GitHub Actions configuration; those are tracked separately in the community issue.

Validation

  • ./hack/generate-configs.sh (run twice; output is idempotent)
  • cd tools/configgen && go test ./...
  • Verified no retiring-repository job files or explicit active repository references remain in Prow configuration.
  • git diff HEAD --check

@knative-prow
knative-prow Bot requested review from cardil and upodroid November 1, 2026 15:20
@knative-prow knative-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 1, 2026
@dprotaso

dprotaso commented Nov 1, 2026

Copy link
Copy Markdown
Member Author

/hold

@knative-prow knative-prow Bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Nov 1, 2026
@dprotaso dprotaso changed the title Remove release jobs for retiring repositories Remove all Prow configuration for retiring repositories Nov 1, 2026
@aliok

aliok commented Nov 2, 2026

Copy link
Copy Markdown
Member

/lgtm

@knative-prow knative-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 2, 2026
@dprotaso

dprotaso commented Nov 3, 2026 •

Copy link
Copy Markdown
Member Author

Rebased on main and checked for anything new since v1.24. Nothing else to remove — the PR already covers the v1.24 jobs and main branch CI for the retiring repos.

Config generation is clean, configgen tests pass, and diff checks are clean.

Leaving this on hold for now.

@knative-prow knative-prow Bot removed the lgtm Indicates that a PR is ready to be merged. label Nov 3, 2026
@dprotaso
dprotaso force-pushed the dprotaso/remove-retired-release-jobs branch from 66552a8 to 3a63ea1 Compare November 3, 2026 03:53
@dprotaso

dprotaso commented Nov 3, 2026

Copy link
Copy Markdown
Member Author

@aliok this needs another /lgtm

@aliok

aliok commented Nov 3, 2026

Copy link
Copy Markdown
Member

/lgtm
/approve

Leaving the unhold to others

@knative-prow knative-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Nov 3, 2026
@knative-prow

knative-prow Bot commented Nov 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, dprotaso

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

The pull request process is described here

Details 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

@knative-prow-robot knative-prow-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 4, 2026
@knative-prow-robot

Copy link
Copy Markdown
Contributor

PR needs rebase.

Details

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants