Skip to content

Latest commit

 

History

History
109 lines (77 loc) · 3.57 KB

README.md

File metadata and controls

109 lines (77 loc) · 3.57 KB
Raw

Release creation

Note 1 Run all scripts from the root of the repository.

Note 2 The main branch in this repo is used as a stash for openshift-specific files needed for CI. Those files are copied to release branches which is where CI operates.

Setting up your clone

Note Your clone must be in $GOPATH/src/knative.dev/eventing not github.com/knative/eventing or openshift-knative/eventing

You must have remotes named "upstream" and "openshift" for the scripts in this repo to work, like this:

git remote add openshift [email protected]:openshift-knative/eventing.git
git remote add upstream [email protected]:knative/eventing.git

Branching

On the main branch create a release branch and then push it upstream:

./openshift/release/create-release-branch.sh vX.Y.Z release-vX.Y.Z
git push -v openshift refs/heads/release-vX.Y.Z\:refs/heads/release-vX.Y.Z

This creates and checks out "release-vX.Y.Z" based on tag "vX.Y.Z" and adds OpenShift specific files that we need to run CI.

All remaining steps must be done on the release branch.

Building image and docker files

On the release branch, build the images and docker files.

make install && make generate-release

If any are new/changed, check them in.

Update CI configuration

To enable CI, you need to update files on the master branch of github.com/openshift/release. This command will update the files, assuming that you have an openshift/release clone in the same tree as this repository; if not add OPENSHIFT=

make update-ci VERSION=X.Y.Z

This creates and modifies files in the openshift/release repo, verify that those files are as expected, commit and create a PR for them. That will start a CI job.

Add/Verify periodic reporter_config

In the openshift/release periodic files, we need to add/verify that the reporter config for slack has been added. There is a reporter_config per OCP release.

For example, for knative-eventing-v0.20.0 we added two reporter_config's to ci-operator/jobs/openshift-knative/eventing/openshift-knative-eventing-release-v0.20.0-periodics.yaml

  name: periodic-ci-openshift-knative-eventing-release-v0.20.0-47-e2e-aws-ocp-47-continuous
  reporter_config:
    slack:
      channel: '#knative-eventing'
      job_states_to_report:
      - success
      - failure
      - error
      report_template: '{{if eq .Status.State "success"}} :rainbow: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> :rainbow: {{else}} :volcano: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> :volcano: {{end}}'

and

  name: periodic-ci-openshift-knative-eventing-release-v0.20.0-46-e2e-aws-ocp-46-continuous
  reporter_config:
    slack:
      channel: '#knative-eventing'
      job_states_to_report:
      - success
      - failure
      - error
      report_template: '{{if eq .Status.State "success"}} :rainbow: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> :rainbow: {{else}} :volcano: Job *{{.Spec.Job}}* ended with *{{.Status.State}}*. <{{.Status.URL}}|View logs> :volcano: {{end}}'

Add these if needed.

Update this README

If you find that any of the steps are incorrect or out of date.

Updating a branch that follow upstream's HEAD

This is done via the nightly Jenkins job to create the release-next branch:

./openshift/release/update-to-head.sh release-vX.Y.Z

This pulls the latest main from upstream, rebase the current fixes on the release-vX.Y.Z branch and updates the Openshift specific files if necessary.