3 ms·

Same here. I even sometimes catch myself being kind of happy about incidents like this happening, because every single one gets us closer to the tipping point a

Same here. I even sometimes catch myself being kind of happy about incidents like this happening, because every single one gets us closer to the tipping point at which companies staying away from third-party cloud services requiring getting unfettered access to some of their crown jewels (code, code documentation, issue data) finally have a serious moat again. Incentives are currently misaligned in my opinion, mostly because of marketing hype around everything cloud-based and still too little consciousness about the long-term consequences of outsourcing core competencies to whatever cloud service is currently hyped the most. Our company is currently looking into alternatives to Jira due to Atlassian going the cloud-only route. One of the must-haves for whatever replaces Jira is a possibility for an on-premise installation. It's still early in the decision phase, but a surprisingly large number of candidates has already been ruled out due to this seemingly-simple requirement.

watermelon0 6y ago
Does your company really have enough people with the knowledge of how to securely run Jira/CI/GitHub/etc. tools, with minimal downtime, and with proper backups? I'm sure there are companies out there where this is possible, but most of them (I'd wager it's more like 99%) won't be able to match cloud-based solutions.
- u801e 6y ago
  > Does your company really have enough people with the knowledge of how to securely run Jira/CI/GitHub/etc. tools, with minimal downtime, and with proper backups? Years ago, many companies ran similar services in house and having downtime wasn't a common scenario.
- Slartie 6y ago
  It actually has been running Jira on premise with zero unannounced downtime for ten years. So...yes, I think that's not the problem to simply continue doing what we did for the last decade. CI and GitLab infrastructure are the same story: run on premise on our own hardware for a decade, with only very minor downtime. It has also evolved from simple isolated Jenkins instances with manually configured build jobs to a shared build/CI cluster using containerization and a lot of automation for build job management. And it's not that we have an abundance of administrative people. A team of three (sometimes being temporarily buffed up with a few more if large infrastructural tasks are planned) for about 200 developers in total. I have a different suspicion: a lot of companies out there have simply forgotten that they are perfectly able to run such services for themselves. Having people telling them all the time that they wouldn't ever be able to do that anyway (with a lot of them having their personal agenda, for example being employed by a cloud service provider) doesn't make things better in that regard.

watermelon0 6y ago

Does your company really have enough people with the knowledge of how to securely run Jira/CI/GitHub/etc. tools, with minimal downtime, and with proper backups? I'm sure there are companies out there where this is possible, but most of them (I'd wager it's more like 99%) won't be able to match cloud-based solutions.

u801e 6y ago
> Does your company really have enough people with the knowledge of how to securely run Jira/CI/GitHub/etc. tools, with minimal downtime, and with proper backups? Years ago, many companies ran similar services in house and having downtime wasn't a common scenario.
Slartie 6y ago
It actually has been running Jira on premise with zero unannounced downtime for ten years. So...yes, I think that's not the problem to simply continue doing what we did for the last decade. CI and GitLab infrastructure are the same story: run on premise on our own hardware for a decade, with only very minor downtime. It has also evolved from simple isolated Jenkins instances with manually configured build jobs to a shared build/CI cluster using containerization and a lot of automation for build job management. And it's not that we have an abundance of administrative people. A team of three (sometimes being temporarily buffed up with a few more if large infrastructural tasks are planned) for about 200 developers in total. I have a different suspicion: a lot of companies out there have simply forgotten that they are perfectly able to run such services for themselves. Having people telling them all the time that they wouldn't ever be able to do that anyway (with a lot of them having their personal agenda, for example being employed by a cloud service provider) doesn't make things better in that regard.