Live data from Hacker News

Atlassian prepares to abandon on-prem server products

theregister.com

111–120 of 205 posts

Re: Atlassian prepares to abandon on-prem server products

#111
post #75
post #66

Earlier quoted context omitted.

Could you share what markdown/git tooling you've identified?

Not speaking for the GP. I use MkDocs and keep my personal notes. The only weak spot for me is that I haven't fully grokked search and as my notes grow, it can be harder to find things. I alternate between figuring out how search and how to bolt on some other search utility. MkDocs includes a utility to publish to Github pages but I keep my notes on a self hosted Gitea server and serve using "python -m http".

Take a look at mkdocs-material, it's not just a theme, it adds some local-side search as well. Still with fully static pages.

Re: Atlassian prepares to abandon on-prem server products

#112

Jira/Confluence are two products that have gotten markedly slower and slower over time and as they've moved into the cloud. I observe load times that remind me of the 90s sometimes using their cloud apps. Incredible they are killing on-prem, but maybe it makes it harder to compare to the slow as molasses cloud offering that way?

>Jira/Confluence

Never quite realized these were the same company. Mostly because they were forced on us, we basically did the bare minimum on those platforms, and they never took off.

Re: Atlassian prepares to abandon on-prem server products

#113

Earlier quoted context omitted.

YouTrack by Jetbrains is very good

Can anyone speak about YouTrack/Space's warts? The marketing blurbs makes Space + YouTrack look like a decent replacement for Jira + Confluence + Bitbucket, but I don't recall ever hearing a developer talk about it.

YouTrack is pretty great. So is TeamCity and they integrate well. The JetBrains instance is open so you can just sign up for an account there and play with it. Also you can run them both on-prem and they're pretty easy to admin if you do.

Space I haven't used. It seems like an attempt to reinvent both products in a GitLab style product which is a pity because the JetBrains tools are very mature and I don't think they needed a new product.

Re: Atlassian prepares to abandon on-prem server products

#114

This is misleading because you can still buy the data center version which replaced the server version.

I can't because it's much more expensive than my company can afford.

No disagreement there at all. Data center is pricey. I imagine if your company can afford some of the licenses on the other products to go non-Cloud such as BitBucket or Bamboo then that may be your answer.

Or go completely open source

Re: Atlassian prepares to abandon on-prem server products

#115
post #75
post #66

Earlier quoted context omitted.

Could you share what markdown/git tooling you've identified?

Not speaking for the GP. I use MkDocs and keep my personal notes. The only weak spot for me is that I haven't fully grokked search and as my notes grow, it can be harder to find things. I alternate between figuring out how search and how to bolt on some other search utility. MkDocs includes a utility to publish to Github pages but I keep my notes on a self hosted Gitea server and serve using "python -m http".

Has anyone identified an easy/feasible way to add SSO authentication to github pages?

Re: Atlassian prepares to abandon on-prem server products

#116
We(as in everyone) are in a serious need of a new git server product. Just do git serving, and do it well. Preferably in a way multiple nodes can be run active-active for scaling and reliability. No need for cicd (Jenkins is fine for that, thank you very much).

What are minimum viable features for me? Granular (per branch) security access. Integration with AD federation and other auth providers(congnito, aws iam) and ability to give AD groups rights.

Web hooks sending and receiving. For example launch a merge request webhook(to lambda via aws api gateway, or to Jenkins). Receive a webhook as merge request approval when some Jenkins job finishes.

There is exactly zero need for your repository system also run cicd jobs. It ends up doing both tasks badly.

You'd like an example of said badness? Ok, how about this: in gitlab enterprise if you create cicd jobs/pipelines there is no way to giving someone an ability to run that pipeline without giving that person ability to push to the repository and submit merge requests. Yes, you can then set it so approval is needed before merge, protecting said pipeline, but why? There has been a ticket on gitlabs own issues page about it for years and it is still not resolved.

But wait, there is more... Gitlab enterprise has no mode of working that let's you have more than one active server at a time so goodbye horizontal scaling.

You want to scale your cicd worker nodes? They want you to use docker mashine(a deprecated product) instead of writing a Plugin like ec2-fleet for Jenkins.

It is obvious gitlab tries to funnel it's enterprise customers into saas.

Re: Atlassian prepares to abandon on-prem server products

#117

One day the pendulum will swing back in the other direction. Until then, those of us who disagree with putting absolutely everything into the cloud will just have to sit back and bide our time.

Not gonna happen unless a new server OS arrives that's significantly easier to use than Linux.

The core diff between on-prem and cloud isn't where the data is hosted. It's that in one case someone else handles UNIX BS and in the other case you do. Get a MacOS-equivalent level of usability for servers in a form that isn't rent it by the hour, and you could see such a migration, but what's the incentive for anyone to build or support that when people are willing to pay so much for cloud services?

Re: Atlassian prepares to abandon on-prem server products

#118

Earlier quoted context omitted.

ADO is the death knell to collaborative modern teams. Who the f wants to waste their day with that UX and feature set?

ADO makes me yearn for Jira because of how slow and clunky it is.

Having been forced to daily drive both for the past few years, I'd take DevOps over Jira any day. Neither is great, but DevOps has had 100% fewer incidents of adding a comment to the wrong issue because of a dog slow UI that's chock full of race conditions.

Re: Atlassian prepares to abandon on-prem server products

#119

The problem with Jira is that we don't have many alternatives at enterprise level. Maybe for smaller teams ( I had a lot of hopes for Github Issues [0] but since they announced the product on last year's Universe event, there were not many news. Maybe this November they will come back with an update. At this point, I feel Jira is like WordPress. It maybe slow and overbloated, but you can have absolutely any plugin an…

It's really hard to find any product or suite of products that replaces Atlassians offerings. Sure you can easily find a issue tracker product, but can it be a service desk at the same time? Bitbucket, Confluence and Jira also integrates really really well. You can have entire workflows that just makes sense, link to documentation, pull-requests/commits and tickets. I've frequently used this setup in a ITIL environme…

You can configure JetBrains TeamCity to be a service desk and competent issue tracker, it also has a Confluence-style knowledge base in the latest versions.

Re: Atlassian prepares to abandon on-prem server products

#120

Earlier quoted context omitted.

On prem is not being killed. They still have the data center products "To be clear, we have no plans to end of life or end of support for our Data Center offering." https://community.atlassian.com/t5/Data-Center-articles/The-...

I have less than 50 seats - they're killing it for me. But I guess one less thing for me to administer.

If there’s one thing I love, it’s waiting on vendors when issues are happening.
Post reply on HN