openshift
USHIFT-6106: Adding optional scenarios to releases directory
@kasturinarra: This pull request references USHIFT-6106 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.
In response to this:
Adding three more scenarios based on the discussion 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 openshift-eng/jira-lifecycle-plugin repository.
With these 3 new scenarios you are adding will have 30 scenarios in releases repository. This is around the limit of hypervisor resources, so I'd suggest removing the 2 scenarios you added for standard suites in https://github.com/openshift/microshift/pull/5695/ PR in favor of the new 2 standard scenarios with the upgrade.
With these 3 new scenarios you are adding will have 30 scenarios in releases repository. This is around the limit of hypervisor resources, so I'd suggest removing the 2 scenarios you added for standard suites in #5695 PR in favor of the new 2 standard scenarios with the upgrade.
@agullon ah looking back i think i misunderstood... let me remove the upgrade as they are really not necessary for now.
@kasturinarra do you mind to change the PR title to avoid confusion? it says three scenarios, but in the final implementations there's only one
@kasturinarra: This pull request references USHIFT-6106 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.
In response to this:
Adding optional scenario to releases directory
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 openshift-eng/jira-lifecycle-plugin repository.