61–70 of 305 posts
Are there good self-hosted alternatives for those of use who'd like to get off of Atlassian products? For Bamboo, I immediately think of Jenkins, although it's showing its age now. For Confluence, I think of Media Wiki. For BitBucket, I think of self-hosted GitLab. Not sure about Jira or Service Desk, though. I'd appreciate any better suggestions.
(It's my start-up.)
We're using Jira, Confluence, and BitBucket on-prem at our DC now, on some pretty sizeable VM's with good network connectivity back to head office. Despite that, it feels very slow. Not the occasional 10+ second page load, where you've accidentally clicked something that happens to generate a cascade of cache misses. I can forgive that kind of infrequent performance hiccup. But rather, regular usage, especially of Co…
We're using Jira, Confluence, and BitBucket on-prem at our DC now, on some pretty sizeable VM's with good network connectivity back to head office. Despite that, it feels very slow. Not the occasional 10+ second page load, where you've accidentally clicked something that happens to generate a cascade of cache misses. I can forgive that kind of infrequent performance hiccup. But rather, regular usage, especially of Co…
Atlassian does not provide particularly good guidance on how to get their tools to perform well. The first big issue for any moderately busy system is that you need to dedicate huge gobs of heap memory (think 16G+) to the tool. After that, they suffer from poor schema design - there are tables that are literally missing indexes on commonly queried columns, and some columns that have delimited values embedded in them.…
I always wondered that, too! Like, you'd think that if you have devs building a product and a team running a hosted instance of the product in the same company, that they'd have a very good feedback loop and make it easy to run the thing and to do it well. Although, I wonder if the answer is that it's not the same product - like with bitbucket, where the thing they run in the cloud isn't the same thing as they sell for on-prem. Or even a lighter version (BB, AFAIK, is literally 2 separate codebases), where they cut features in order to make the cloud version work.
> It's hard for me to see how "Java" and "cloud" go together.
Nah, it's not Java, it's the specific product. I've worked at a SaaS shop that did all Java, and while the pathological cases are comically bad, it's actually fine most of the time IME.
Thank goodness! The unicorn I work for will finally ditch JIRA and move on to something more user-friendly. What a relief.
This is entirely because they had to fork their product and codebase between cloud and on-prem, and their resulting total failure on execution on their internal product roadmap. Atlasssian has demonstrated a chronic inability over the past few years to maintain feature parity between what are effectively two different products. Atlasssian has had a really, really terrible feature execution delivery pace over the past…
It's insane that they had to that rather than giving their On-Prem version the ability to scale the way you need a SaaS service to scale. Turning your SaaS Ops team into an On-Prem customer is a great way to dog-food your product.
In fact, it gets tricky as you have "location-flagged" functionality depending upon Cloud or Self-hosted.
We did this from scratch @ Documize by making (bold?) choices around deployment/runtime and database schema design for both SaaS and self-hosted "products":
- run the exact same binary (we used Golang)
- share/use the exact same database schema
- data migration process the same for schema changes
- support multi-tenanting: "enterprise" self-hosted also multi-tenanting so different teams/departments internally get different URLs
- use the same "build" process to compile and ship
Probably plenty more I could tell you!
We use Bitbucket server because we prefer the code review UI and the diff views over everything else. I was shocked when I tried the cloud version and saw how different and how much worse it was. Would otherwise actually prefer to move to cloud but not with that UI, will re-eval competitors instead.
RIP defense community using Jira
Earlier quoted context omitted.
It's insane that they had to that rather than giving their On-Prem version the ability to scale the way you need a SaaS service to scale. Turning your SaaS Ops team into an On-Prem customer is a great way to dog-food your product.
It's not easy unless you begin with that mind-set from day one. In fact, it gets tricky as you have "location-flagged" functionality depending upon Cloud or Self-hosted. We did this from scratch @ Documize by making (bold?) choices around deployment/runtime and database schema design for both SaaS and self-hosted "products": - run the exact same binary (we used Golang) - share/use the exact same database schema - dat…
This sounds like a terrible move and will probably force all medium-size organizations I work with to ditch Atlassian. We have the technical know-how to administer data center versions of their products, but we can’t do shit if they force potential customers to pay for a minimum of 40 000 USD for a license per product. Many of these orgs have multiple Atlassian products so this will probably end up doubling costs on…
Microsoft already has GitHub that works fine as a Jira/Confluence substitute for technical people. Maybe this will be their call to make it more accessable.