-
Notifications
You must be signed in to change notification settings - Fork 4
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
Rancher-2025: Add deployment status checking on module stages #788
base: RANCHER-1334
Are you sure you want to change the base?
Conversation
@@ -9,7 +9,7 @@ import org.folio.models.parameters.CypressTestsParameters | |||
import org.jenkinsci.plugins.workflow.libs.Library | |||
|
|||
//TODO remove branch before merge to master | |||
@Library('pipelines-shared-library@RANCHER-1334') _ | |||
@Library('pipelines-shared-library') _ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -27,8 +27,7 @@ resource "helm_release" "opensearch-single-node" { | |||
values = [<<-EOF | |||
image: | |||
tag: 2.11.0 | |||
registry: 732722833398.dkr.ecr.us-west-2.amazonaws.com | |||
repository: opensearch | |||
repository: 732722833398.dkr.ecr.us-west-2.amazonaws.com/opensearch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch!
@@ -176,6 +176,7 @@ void call(CreateNamespaceParameters args) { | |||
stage('[Helm] Deploy mgr-*') { | |||
folioHelm.withKubeConfig(namespace.getClusterName()) { | |||
folioHelm.deployFolioModulesParallel(namespace, namespace.getModules().getMgrModules()) | |||
folioHelm.checkDeploymentsRunning(namespace.getNamespaceName(), namespace.getModules().getMgrModules()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make env provisioning more longer, put this kind of check in every single deployment, if it really required, but for mgr-* kind of deployments, which are very basic, do we need these checks...?
No description provided.