test: run the development environment steps in CI (#14025)

* test: run the development environment steps in CI

Exercise some of our `Makefile`, `docker-compose.yml` and shell script
wrapper utilities.

Originally conceived in #10052, simplified with current commands.

Closes #10052

Signed-off-by: Mike Fiedler <[email protected]>

* Add a start_period to the db healthcheck

Allow some time for the database to start up before performing "real"
readiness checks.

If the service is ready (healthcheck test command passes) during the
start_period, it'll be considered healthy and continue.

Refs: https://docs.docker.com/engine/reference/builder/#healthcheck:~:text=start%20period%20provides%20initialization%20time%20for%20containers%20that%20need,will%20be%20counted%20towards%20the%20maximum%20number%20of%20retries.

Signed-off-by: Mike Fiedler <[email protected]>

* only run on a schedule, and not part of PR/flow

Signed-off-by: Mike Fiedler <[email protected]>

---------

Signed-off-by: Mike Fiedler <[email protected]>

Author: miketheman

.github/workflows/dev-env-test.yml

@@ -0,0 +1,18 @@
+name: Development Environment
+
+on:
+  schedule:
+    - cron: '0 13 * * *'  # once a day at around 9am eastern
+  workflow_dispatch:
+
+jobs:
+  build:
+    # TODO: Should we test on other platforms like Windows and Mac?
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - run: make build
+      - run: docker compose up -d
+      - run: docker compose ps
+      - run: make initdb
+      - run: make tests

docker-compose.yml

@@ -37,6 +37,7 @@ services:
     healthcheck:
       test: ["CMD", "pg_isready", "-U", "postgres", "-d", "postgres"]
       interval: 1s
+      start_period: 10s
 
   stripe:
     image: stripe/stripe-mock:v0.162.0