... and you have to CI your Jira too!
I've just received a patch for jrawio from a user. Great stuff. But the user complained about the fact he could log in on my Jira (jrawio uses my own installation at Tidalwave), but he couldn't post comments or attach the patch. He's right in complaining, of course. Usually I pay a lot of care with the communication infrastructure for a project, and in the past there were no specific problems with my Jira installation. Now, as I'm changing the world (forge, web site, whatever) I've probably made some misconfiguration. Not a big deal, I'll fix it - but this sounds as the old rule "if you didn't test it, it's broken". Since in the past Jira worked, I assumed it was still working. My bigger mistake is that I wasn't probing it continuously (of course, I'm using Jira all the days, but clearly the problem is not visible with my account).
So, the question is: should I set up some sort of automatic, continuous testing of the infrastructure? Do you do something similar? How?