Introductory ramblings about the title (click to expand)
I wanted to make a little word play on the process I have observed many people have around updating their Drupal sites. People tend to say they don't have time or budget to have CI pipelines or tests, and instead what they do is they "double check" that everything looks ok in a staging environment. I never do that. Instead I have tests and a CI pipeline. For example. I just checked the builds of https://violinist.io, and it has 457 tests. So I went ahead and asked Chat GPT to help me a bit:
If I checked something twice I double checked. If I checked it 3 times I triple checked. 4 times quadruple checked. What would 457 times be then?
Chat GPT told me no one uses it like that, and that it's “grammatically tortured”. I was repeatedly advised against using it:
If you really wanted a made-up but linguistically inspired version:
"Quadringentoheptapentacontuple-checked" (457-checked)
quadringento = 400
hepta =7
pentaconta = 50 But again this is deep into nerdy satire territory, like something you'd read in a Douglas Adams or Terry Pratchett book.
OK, my trusty AI friend. I accept the warning, but being in nerdy satire territory does not sound too bad. So with that introductory explanation of the title out of the way. Let me proceed with helping people increase their Drupal deployment confidence.
My last post about documenting the amount of commits and numbers around automatically updating Drupal projects received a bit of feedback. Most were in the category of surprise or being impressed with the large number. Then I randomly stumbled upon someone discussing the article on LinkedIn.
Emmons Michael Patzer says:
I enjoy his points. would enjoy even more seeing all the project work flow updates he indicates he runs. Lift the hood off some of that magic for the rest of us…
There is an underlying complement there I guess I will take. But the workflows are anything but magic.
Well let's walk through it shall we. First I can list up the checks:
- composer install
- composer validate
- phpcs
- phpstan
- phpunit
- behat
- site install
- site schema
- clean repo check
In a couple short blog posts I will attempt to recreate this setup in the three major version control providers (GitHub, GitLab and Bitbucket) and let's see how magic it feels then?
The repository will be a simple Drupal site with a couple of contrib modules, and one custom module. The repos can be found here:
https://github.com/eiriksm/drupal-confidence
https://bitbucket.org/eirikmorland/drupal-confidence
https://gitlab.com/eiriksm/drupal-confidence
I'm going to finish this blog with an animated gif, supposedly being a result for the search term "Quadringentoheptapentacontuple"
Do you want to comment?
This article uses github for commenting. To comment, you can visit https://github.com/eiriksm/eiriksm.dev-comments/issues/24.