Updated snapshots.

Author: AlexSkrypnyk

.vortex/installer/tests/Fixtures/handler_process/ciprovider_circleci/.circleci/config.yml

@@ -7,15 +7,6 @@
 # containers defined in `docker-compose.yml` run on a *remote* Docker server
 # controlled by CircleCI.
 # The "runner" container uses Docker client to control the remote Docker server.
-#
-# Scheduled pipelines:
-# The `nightly-db` workflow requires a schedule trigger configured in CircleCI UI.
-# Go to Project Settings > Triggers > Add Scheduled Trigger:
-#   - Trigger name: nightly-db
-#   - Config source: config.yml
-#   - Branch: develop
-#   - Schedule: Every day at 18:00 UTC (or a custom time)
-# See https://www.vortextemplate.com/docs/continuous-integration/circleci
 version: '2.1'
 
 aliases:
@@ -27,6 +18,9 @@ aliases:
   # Replace this key fingerprint with your own and remove this comment.
   - &deploy_ssh_fingerprint "SHA256:6d+U5QubT0eAWz+4N2wt+WM2qx6o4cvyvQ6xILETJ84"
 
+  # Schedule to run nightly database build (to cache the database for the next day).
+  - &nightly_db_schedule "0 18 * * *"
+
   # Shared runner container configuration applied to each job.
   - &runner_config
     working_directory: &working_directory ~/project
@@ -482,9 +476,6 @@ jobs:
 workflows:
   # Commit workflow. Runs for every commit push to the remote repository.
   commit:
-    when:
-      not:
-        equal: [scheduled_pipeline, << pipeline.trigger_source >>]
     jobs:
       - database:
           filters:
@@ -527,11 +518,13 @@ workflows:
               only: /^[0-9]+(\.[0-9]+){2}(-rc\.[0-9]+)?$|^[0-9]{4}-[0-9]{2}-[0-9]{2}(\.[0-9]+)?$/
 
   # Nightly database workflow runs overnight to capture fresh database and cache it.
-  # Requires a "nightly-db" schedule trigger configured in CircleCI UI.
   nightly-db:
-    when:
-      and:
-        - equal: [scheduled_pipeline, << pipeline.trigger_source >>]
-        - equal: ["nightly-db", << pipeline.schedule.name >>]
+    triggers:
+      - schedule:
+          cron: *nightly_db_schedule
+          filters:
+            branches:
+              only:
+                - develop
     jobs:
       - database-nightly

.vortex/installer/tests/Fixtures/handler_process/deploy_types_all_circleci/.circleci/config.yml

@@ -7,15 +7,6 @@
 # containers defined in `docker-compose.yml` run on a *remote* Docker server
 # controlled by CircleCI.
 # The "runner" container uses Docker client to control the remote Docker server.
-#
-# Scheduled pipelines:
-# The `nightly-db` workflow requires a schedule trigger configured in CircleCI UI.
-# Go to Project Settings > Triggers > Add Scheduled Trigger:
-#   - Trigger name: nightly-db
-#   - Config source: config.yml
-#   - Branch: develop
-#   - Schedule: Every day at 18:00 UTC (or a custom time)
-# See https://www.vortextemplate.com/docs/continuous-integration/circleci
 version: '2.1'
 
 aliases:
@@ -27,6 +18,9 @@ aliases:
   # Replace this key fingerprint with your own and remove this comment.
   - &deploy_ssh_fingerprint "SHA256:6d+U5QubT0eAWz+4N2wt+WM2qx6o4cvyvQ6xILETJ84"
 
+  # Schedule to run nightly database build (to cache the database for the next day).
+  - &nightly_db_schedule "0 18 * * *"
+
   # Shared runner container configuration applied to each job.
   - &runner_config
     working_directory: &working_directory ~/project
@@ -482,9 +476,6 @@ jobs:
 workflows:
   # Commit workflow. Runs for every commit push to the remote repository.
   commit:
-    when:
-      not:
-        equal: [scheduled_pipeline, << pipeline.trigger_source >>]
     jobs:
       - database:
           filters:
@@ -527,11 +518,13 @@ workflows:
               only: /^[0-9]+(\.[0-9]+){2}(-rc\.[0-9]+)?$|^[0-9]{4}-[0-9]{2}-[0-9]{2}(\.[0-9]+)?$/
 
   # Nightly database workflow runs overnight to capture fresh database and cache it.
-  # Requires a "nightly-db" schedule trigger configured in CircleCI UI.
   nightly-db:
-    when:
-      and:
-        - equal: [scheduled_pipeline, << pipeline.trigger_source >>]
-        - equal: ["nightly-db", << pipeline.schedule.name >>]
+    triggers:
+      - schedule:
+          cron: *nightly_db_schedule
+          filters:
+            branches:
+              only:
+                - develop
     jobs:
       - database-nightly

.vortex/installer/tests/Fixtures/handler_process/deploy_types_none_circleci/.circleci/config.yml

@@ -7,15 +7,6 @@
 # containers defined in `docker-compose.yml` run on a *remote* Docker server
 # controlled by CircleCI.
 # The "runner" container uses Docker client to control the remote Docker server.
-#
-# Scheduled pipelines:
-# The `nightly-db` workflow requires a schedule trigger configured in CircleCI UI.
-# Go to Project Settings > Triggers > Add Scheduled Trigger:
-#   - Trigger name: nightly-db
-#   - Config source: config.yml
-#   - Branch: develop
-#   - Schedule: Every day at 18:00 UTC (or a custom time)
-# See https://www.vortextemplate.com/docs/continuous-integration/circleci
 version: '2.1'
 
 aliases:
@@ -27,6 +18,9 @@ aliases:
   # Replace this key fingerprint with your own and remove this comment.
   - &deploy_ssh_fingerprint "SHA256:6d+U5QubT0eAWz+4N2wt+WM2qx6o4cvyvQ6xILETJ84"
 
+  # Schedule to run nightly database build (to cache the database for the next day).
+  - &nightly_db_schedule "0 18 * * *"
+
   # Shared runner container configuration applied to each job.
   - &runner_config
     working_directory: &working_directory ~/project
@@ -424,9 +418,6 @@ jobs:
 workflows:
   # Commit workflow. Runs for every commit push to the remote repository.
   commit:
-    when:
-      not:
-        equal: [scheduled_pipeline, << pipeline.trigger_source >>]
     jobs:
       - database:
           filters:
@@ -440,11 +431,13 @@ workflows:
               only: /.*/
 
   # Nightly database workflow runs overnight to capture fresh database and cache it.
-  # Requires a "nightly-db" schedule trigger configured in CircleCI UI.
   nightly-db:
-    when:
-      and:
-        - equal: [scheduled_pipeline, << pipeline.trigger_source >>]
-        - equal: ["nightly-db", << pipeline.schedule.name >>]
+    triggers:
+      - schedule:
+          cron: *nightly_db_schedule
+          filters:
+            branches:
+              only:
+                - develop
     jobs:
       - database-nightly

.vortex/installer/tests/Fixtures/handler_process/deps_updates_provider_ci_circleci/.circleci/config.yml

@@ -7,15 +7,6 @@
 # containers defined in `docker-compose.yml` run on a *remote* Docker server
 # controlled by CircleCI.
 # The "runner" container uses Docker client to control the remote Docker server.
-#
-# Scheduled pipelines:
-# The `nightly-db` workflow requires a schedule trigger configured in CircleCI UI.
-# Go to Project Settings > Triggers > Add Scheduled Trigger:
-#   - Trigger name: nightly-db
-#   - Config source: config.yml
-#   - Branch: develop
-#   - Schedule: Every day at 18:00 UTC (or a custom time)
-# See https://www.vortextemplate.com/docs/continuous-integration/circleci
 version: '2.1'
 
 aliases:
@@ -27,6 +18,9 @@ aliases:
   # Replace this key fingerprint with your own and remove this comment.
   - &deploy_ssh_fingerprint "SHA256:6d+U5QubT0eAWz+4N2wt+WM2qx6o4cvyvQ6xILETJ84"
 
+  # Schedule to run nightly database build (to cache the database for the next day).
+  - &nightly_db_schedule "0 18 * * *"
+
   # Shared runner container configuration applied to each job.
   - &runner_config
     working_directory: &working_directory ~/project
@@ -482,9 +476,6 @@ jobs:
 workflows:
   # Commit workflow. Runs for every commit push to the remote repository.
   commit:
-    when:
-      not:
-        equal: [scheduled_pipeline, << pipeline.trigger_source >>]
     jobs:
       - database:
           filters:
@@ -527,11 +518,13 @@ workflows:
               only: /^[0-9]+(\.[0-9]+){2}(-rc\.[0-9]+)?$|^[0-9]{4}-[0-9]{2}-[0-9]{2}(\.[0-9]+)?$/
 
   # Nightly database workflow runs overnight to capture fresh database and cache it.
-  # Requires a "nightly-db" schedule trigger configured in CircleCI UI.
   nightly-db:
-    when:
-      and:
-        - equal: [scheduled_pipeline, << pipeline.trigger_source >>]
-        - equal: ["nightly-db", << pipeline.schedule.name >>]
+    triggers:
+      - schedule:
+          cron: *nightly_db_schedule
+          filters:
+            branches:
+              only:
+                - develop
     jobs:
       - database-nightly

.vortex/installer/tests/Fixtures/handler_process/migration_disabled_circleci/.circleci/config.yml

@@ -7,15 +7,6 @@
 # containers defined in `docker-compose.yml` run on a *remote* Docker server
 # controlled by CircleCI.
 # The "runner" container uses Docker client to control the remote Docker server.
-#
-# Scheduled pipelines:
-# The `nightly-db` workflow requires a schedule trigger configured in CircleCI UI.
-# Go to Project Settings > Triggers > Add Scheduled Trigger:
-#   - Trigger name: nightly-db
-#   - Config source: config.yml
-#   - Branch: develop
-#   - Schedule: Every day at 18:00 UTC (or a custom time)
-# See https://www.vortextemplate.com/docs/continuous-integration/circleci
 version: '2.1'
 
 aliases:
@@ -27,6 +18,9 @@ aliases:
   # Replace this key fingerprint with your own and remove this comment.
   - &deploy_ssh_fingerprint "SHA256:6d+U5QubT0eAWz+4N2wt+WM2qx6o4cvyvQ6xILETJ84"
 
+  # Schedule to run nightly database build (to cache the database for the next day).
+  - &nightly_db_schedule "0 18 * * *"
+
   # Shared runner container configuration applied to each job.
   - &runner_config
     working_directory: &working_directory ~/project
@@ -482,9 +476,6 @@ jobs:
 workflows:
   # Commit workflow. Runs for every commit push to the remote repository.
   commit:
-    when:
-      not:
-        equal: [scheduled_pipeline, << pipeline.trigger_source >>]
     jobs:
       - database:
           filters:
@@ -527,11 +518,13 @@ workflows:
               only: /^[0-9]+(\.[0-9]+){2}(-rc\.[0-9]+)?$|^[0-9]{4}-[0-9]{2}-[0-9]{2}(\.[0-9]+)?$/
 
   # Nightly database workflow runs overnight to capture fresh database and cache it.
-  # Requires a "nightly-db" schedule trigger configured in CircleCI UI.
   nightly-db:
-    when:
-      and:
-        - equal: [scheduled_pipeline, << pipeline.trigger_source >>]
-        - equal: ["nightly-db", << pipeline.schedule.name >>]
+    triggers:
+      - schedule:
+          cron: *nightly_db_schedule
+          filters:
+            branches:
+              only:
+                - develop
     jobs:
       - database-nightly

.vortex/installer/tests/Fixtures/handler_process/migration_enabled_circleci/.circleci/config.yml

@@ -7,15 +7,6 @@
 # containers defined in `docker-compose.yml` run on a *remote* Docker server
 # controlled by CircleCI.
 # The "runner" container uses Docker client to control the remote Docker server.
-#
-# Scheduled pipelines:
-# The `nightly-db` workflow requires a schedule trigger configured in CircleCI UI.
-# Go to Project Settings > Triggers > Add Scheduled Trigger:
-#   - Trigger name: nightly-db
-#   - Config source: config.yml
-#   - Branch: develop
-#   - Schedule: Every day at 18:00 UTC (or a custom time)
-# See https://www.vortextemplate.com/docs/continuous-integration/circleci
 version: '2.1'
 
 aliases:
@@ -27,6 +18,9 @@ aliases:
   # Replace this key fingerprint with your own and remove this comment.
   - &deploy_ssh_fingerprint "SHA256:6d+U5QubT0eAWz+4N2wt+WM2qx6o4cvyvQ6xILETJ84"
 
+  # Schedule to run nightly database build (to cache the database for the next day).
+  - &nightly_db_schedule "0 18 * * *"
+
   # Shared runner container configuration applied to each job.
   - &runner_config
     working_directory: &working_directory ~/project
@@ -491,9 +485,6 @@ jobs:
 workflows:
   # Commit workflow. Runs for every commit push to the remote repository.
   commit:
-    when:
-      not:
-        equal: [scheduled_pipeline, << pipeline.trigger_source >>]
     jobs:
       - database:
           filters:
@@ -536,11 +527,13 @@ workflows:
               only: /^[0-9]+(\.[0-9]+){2}(-rc\.[0-9]+)?$|^[0-9]{4}-[0-9]{2}-[0-9]{2}(\.[0-9]+)?$/
 
   # Nightly database workflow runs overnight to capture fresh database and cache it.
-  # Requires a "nightly-db" schedule trigger configured in CircleCI UI.
   nightly-db:
-    when:
-      and:
-        - equal: [scheduled_pipeline, << pipeline.trigger_source >>]
-        - equal: ["nightly-db", << pipeline.schedule.name >>]
+    triggers:
+      - schedule:
+          cron: *nightly_db_schedule
+          filters:
+            branches:
+              only:
+                - develop
     jobs:
       - database-nightly

.vortex/installer/tests/Fixtures/handler_process/timezone_circleci/.circleci/config.yml

@@ -7,15 +7,6 @@
 # containers defined in `docker-compose.yml` run on a *remote* Docker server
 # controlled by CircleCI.
 # The "runner" container uses Docker client to control the remote Docker server.
-#
-# Scheduled pipelines:
-# The `nightly-db` workflow requires a schedule trigger configured in CircleCI UI.
-# Go to Project Settings > Triggers > Add Scheduled Trigger:
-#   - Trigger name: nightly-db
-#   - Config source: config.yml
-#   - Branch: develop
-#   - Schedule: Every day at 18:00 UTC (or a custom time)
-# See https://www.vortextemplate.com/docs/continuous-integration/circleci
 version: '2.1'
 
 aliases:
@@ -27,6 +18,9 @@ aliases:
   # Replace this key fingerprint with your own and remove this comment.
   - &deploy_ssh_fingerprint "SHA256:6d+U5QubT0eAWz+4N2wt+WM2qx6o4cvyvQ6xILETJ84"
 
+  # Schedule to run nightly database build (to cache the database for the next day).
+  - &nightly_db_schedule "0 18 * * *"
+
   # Shared runner container configuration applied to each job.
   - &runner_config
     working_directory: &working_directory ~/project
@@ -482,9 +476,6 @@ jobs:
 workflows:
   # Commit workflow. Runs for every commit push to the remote repository.
   commit:
-    when:
-      not:
-        equal: [scheduled_pipeline, << pipeline.trigger_source >>]
     jobs:
       - database:
           filters:
@@ -527,11 +518,13 @@ workflows:
               only: /^[0-9]+(\.[0-9]+){2}(-rc\.[0-9]+)?$|^[0-9]{4}-[0-9]{2}-[0-9]{2}(\.[0-9]+)?$/
 
   # Nightly database workflow runs overnight to capture fresh database and cache it.
-  # Requires a "nightly-db" schedule trigger configured in CircleCI UI.
   nightly-db:
-    when:
-      and:
-        - equal: [scheduled_pipeline, << pipeline.trigger_source >>]
-        - equal: ["nightly-db", << pipeline.schedule.name >>]
+    triggers:
+      - schedule:
+          cron: *nightly_db_schedule
+          filters:
+            branches:
+              only:
+                - develop
     jobs:
       - database-nightly