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.

Sign up for GitHub

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

Jump to bottom

Make the new location of uptest clear #200

Merged
merged 1 commit into from
Mar 26, 2024
Merged

Make the new location of uptest clear #200

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,8 @@
# official-providers-ci

> [!IMPORTANT]
> Uptest framework was contributed to CNCF and now located at https://github.com/crossplane/uptest

Repository for the CI tooling of the Upbound official providers repositories:
- `crddiff`: A tool for checking breaking API changes between two CRD OpenAPI v3 schemas. The schemas can come from either two revisions of a CRD, or from the versions declared in a single CRD.
- `buildtagger`: A tool for generating build tags (constraints) for the source modules of the official provider families.
Expand All @@ -8,16 +12,16 @@ Repository for the CI tooling of the Upbound official providers repositories:
- `updoc`: Upbound enhanced document processor.

This repository is also the home of the Upbound official providers reusable workflows:
- `.github/workflows/provider-ci.yml`: A reusable CI workflow for building, linting & validating the official providers.
- `.github/workflows/pr-comment-trigger.yml`: A reusable workflow for triggering `uptest` runs using a specified set of example manifests via pull request comments.
- `.github/workflows/provider-ci.yml`: A reusable CI workflow for building, linting & validating the official providers.
- `.github/workflows/pr-comment-trigger.yml`: A reusable workflow for triggering `uptest` runs using a specified set of example manifests via pull request comments.
- `.github/workflows/provider-publish-service-artifacts.yml`: A reusable workflow for building the official provider families and pushing their packages to the Upbound registry.
- `.github/workflows/native-provider-bump.yml`: A reusable workflow for bumping the underlying Terraform provider versions of upjet-based official providers.
- `.github/workflows/provider-backport.yml`: A reusable workflow for opening backport PRs in the specified release branches by inspecting the labels on merged PRs.
- `.github/workflows/issue-triage.yml`: A reusable workflow for identifying and labeling issues opened by the community.
- `.github/workflows/pr-triage.yml`: A reusable workflow for identifying and labeling pull requests opened by the community.
- `.github/workflows/provider-tag.yml`: A reusable workflow for tagging commits in the release process.
- `.github/workflows/provider-updoc.yml`: A reusable workflow for running `updoc` and publishing the provider documentation to the [Upbound marketplace](https://marketplace.upbound.io/providers).
- `.github/workflows/scan.yml`: A reusable workflow for running [Trivy](https://trivy.dev) scans in the official provider repositories.
- `.github/workflows/scan.yml`: A reusable workflow for running [Trivy](https://trivy.dev) scans in the official provider repositories.
- `.github/workflows/provider-commands.yml`: A reusable workflow for opening backport PRs in the specified release branches via PR comments.

## Report a Bug
Expand Down
Loading