naveenrajm7 / openshift-knative-hack

CI tooling to improve and automate CI management

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

hack

CI tooling and hacks to improve CI

Generate openshift/release config

  • Add configuration for your repository in config/<file.yaml>
    • If you're adding a new file in config/ directory, add the new file to the make generate-ci command
  • Run make generate-ci ARGS=--remote=<your_remote>
    • For example, make generate-ci ARGS=--remote=git@github.com:pierDipi/release.git
    • If you are using podman, make sure to have export CONTAINER_ENGINE=podman set
  • Create a PR to https://github.com/openshift/release (to be automated)

To generate openshift/release config for a single repository, run the specific task in the Makefile or run individual commands in the Makefile, such as:

go run github.com/openshift-knative/hack/cmd/prowgen --config config/eventing-hyperfoil-benchmark.yaml --remote <your_remote>
# go run github.com/openshift-knative/hack/cmd/prowgen --config config/eventing-hyperfoil-benchmark.yaml --remote git@github.com:aliok/release.git 

This generation works this way:

  • openshift/relase is cloned
  • The target repository is cloned
  • The makefile of the target repository is parsed to find the make targets that match the regex in the config/<file.yaml> files
  • For any matches, 2 tests are generated.
    • One for the presubmit (that runs on PRs on the target repository)
    • One for the periodics (that runs regularly)
  • There are also CI job config generated, which use the tests above.
  • If the matching regex is specified in onDemand field, then the presubmit is marked as optional (always_run: false).

Limitations:

  • It is not currently possible to disable periodics per job

Run unit tests

make unit-tests

Updating OpenShift versions

CI configs use specific OpenShift versions. To change the version, you need to update the YAML files in the config/ directory.

When a new OpenShift version is released, wait until the cluster pool for OpenShift CI is available in https://docs.ci.openshift.org/docs/how-tos/cluster-claim/#existing-cluster-pools.

Troubleshooting

Git not configured to use GPG signing

error: gpg failed to sign the data
fatal: failed to write commit object

You need to configure GPG signing in your git config. See https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key#telling-git-about-your-ssh-key.

If you see this error, you need to update your Git to version 2.34 or later.

error: unsupported value for gpg.format: ssh
fatal: bad config variable 'gpg.format' in file '/Users/<you>/.gitconfig'

About

CI tooling to improve and automate CI management

License:Apache License 2.0


Languages

Language:Go 92.7%Language:Dockerfile 3.7%Language:Makefile 2.1%Language:Shell 1.5%