tvbeek, 5 months ago

@jclermont about not caching the configuration: we have a #CI job that runs a couple of basic commands including config:cache to be sure it doesn't crash during a deployment. (We use #GitLab CI so the jobs only depend on other jobs unless defined)

jclermont, 5 months ago

@tvbeek do you run your tests in CI after caching config? I’m still digging into the particulars, but our tests fail with a cached config.

tvbeek, 5 months ago

@jclermont there isn't any dependency between the jobs so they can be in paralel or an after the other. They don't influence any other job.

jclermont, 5 months ago

@tvbeek got it, that makes sense. So it’s a smoke test that the command runs, you’re not trying to run your tests with the cached environment (though I do recommend running tests with routes cached, I’ll share a bug story tomorrow as to why)

tvbeek, 5 months ago

@jclermont yes indeed, a smoke test is a good explanation for it. And I'm interested in your story 👍

jclermont, 5 months ago

@tvbeek Just posted it: https://phpc.social/@jclermont/111658598054949009

tvbeek, 5 months ago

@jclermont that was an interested bug to find and fix. (And a nice post to read)