Loading...

XML

Word

Printable

Type: Story
Resolution: Obsolete
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: CNV Install, Upgrade and Operators
Labels:
None

Activity Type:
Product / Portfolio Work
Epic Link:
CNV-28638

Regression:
None

SFDC Cases Links:
SFDC Cases Open:
SFDC Cases Counter:

According to https://docs.ci.openshift.org/docs/architecture/branching/#how-do-i-opt-my-repository-into-automated-branching

We have to ensure that the promotion stanza in your ci-operator configuration for your default branch is pointing to the latest OCP release.

currently we already have the promotion stanza in the release branches but not on master.

clones

CNV-26580 enroll github.com/openshift-cnv/cnv-ci into automated branching

Closed

is cloned by

CNV-33288 enroll github.com/openshift-cnv/cnv-ci into automated branching

Closed

CNV-33300 enroll github.com/openshift-cnv/cnv-ci into automated branching

Closed

CNV-33316 enroll github.com/openshift-cnv/cnv-ci into automated branching

Closed

CNV-33323 enroll github.com/openshift-cnv/cnv-ci into automated branching

Closed

Assignee:: Maya Rashish (Inactive)

Reporter:: Simone Tiraboschi

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2023/05/08 9:27 AM

Updated:: 2025/08/05 8:49 PM

Resolved:: 2023/05/17 7:59 AM