From caf71e42b7473ddb8dd289b5f94d39deff5198fe Mon Sep 17 00:00:00 2001 From: Dusty Mabe Date: Wed, 14 Dec 2022 15:29:04 -0500 Subject: [PATCH] openshift-apps: remove build step from a few apps Everytime we run the playbook a new build kicks off, but the app was just restarted. So what happens is we end up with the app getting started twice (once when the deploymentconfig gets updated and once when the build finishes). This could be bad if the app has some startup steps that need to not be interrupted. Let's just manually trigger builds since we have the permissions to do that in the web interface and via the CLI. --- playbooks/openshift-apps/coreos-ostree-importer.yml | 5 ----- playbooks/openshift-apps/fedora-ostree-pruner.yml | 5 ----- 2 files changed, 10 deletions(-) diff --git a/playbooks/openshift-apps/coreos-ostree-importer.yml b/playbooks/openshift-apps/coreos-ostree-importer.yml index 624b575c3a..704d0cb5df 100644 --- a/playbooks/openshift-apps/coreos-ostree-importer.yml +++ b/playbooks/openshift-apps/coreos-ostree-importer.yml @@ -82,11 +82,6 @@ template: buildconfig.yml objectname: buildconfig.yml - - role: openshift/start-build - app: coreos-ostree-importer - buildname: coreos-ostree-importer-build - objectname: coreos-ostree-importer-build - - role: openshift/object app: coreos-ostree-importer template: deploymentconfig.yml diff --git a/playbooks/openshift-apps/fedora-ostree-pruner.yml b/playbooks/openshift-apps/fedora-ostree-pruner.yml index 6a639f4f3d..b0fd836944 100644 --- a/playbooks/openshift-apps/fedora-ostree-pruner.yml +++ b/playbooks/openshift-apps/fedora-ostree-pruner.yml @@ -27,11 +27,6 @@ template: buildconfig.yml objectname: buildconfig.yml - - role: openshift/start-build - app: fedora-ostree-pruner - buildname: fedora-ostree-pruner-build - objectname: fedora-ostree-pruner-build - - role: openshift/object app: fedora-ostree-pruner template: deploymentconfig.yml