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.
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
operators [CI] syndesis (1.11.0) #89
operators [CI] syndesis (1.11.0) #89
Conversation
Signed-off-by: phantomjinx <p.g.richardson@phantomjinx.co.uk>
Hi @phantomjinx. Thanks for your PR. I'm waiting for a redhat-openshift-ecosystem member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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/test-infra repository. |
|
Can you give steerage on this please? I am bringing Syndesis over from upstream-community to here since its openshift-only (posted in the wrong catalog). So 1.9.0 is old now but I wanted to maintain some kind of upgrade graph to 1.11.0 and then add 1.12.0. However, 1.9.0 is using metadata format but we changed over to bundle format in 1.11.0 so tests are failing. How should this be handled, please? Do I need to convert 1.9.0 and 1.7.0 to bundle format first? Thx. |
@phantomjinx, please do not mix formats. The newest version is in bundle format, other versions are in package manifest format. |
So that's the question.... Given we've moved over to the bundle format, should I delete the old versions or update them 1 at a time to bundle format? |
/test all |
@phantomjinx We are supporting only one format for all operators. If you want to upgrade to bundle. Please do it for all versions and remove You can convert all versions to bundle in current PR |
@phantomjinx: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
@phantomjinx can you please resolve conflicts? |
@phantomjinx: PR needs rebase. 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/test-infra repository. |
Superceded by 1.12.0 |
Signed-off-by: Idan Moyal <idan.moyal@elastic.co>
Signed-off-by: phantomjinx p.g.richardson@phantomjinx.co.uk
Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions
Updates to existing Operators
ci.yaml
file according to the update instructions?replaces
property if you chosereplaces-mode
via theupdateGraph
property inci.yaml
?package.yaml
orannotations.yaml
?Your submission should not
Operator Description must contain (in order)
Operator Metadata should contain
Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here