3 ms·

Despite the "Azure" name, Azure DevOps Server (formerly Team Foundation Server), is still a rock-solid on-prem system for git repo hosting, issues/stories/proje

Despite the "Azure" name, Azure DevOps Server (formerly Team Foundation Server), is still a rock-solid on-prem system for git repo hosting, issues/stories/projects, build automation, and the rest - though I feel it has stagnated somewhat, and git integration still feels half-baked compared to TFS's previous SVN-clone, but is still my first-choice for on-prem installs (granted, I'm still wedded to the MSFT stack).

whoopsie 3y ago
ADO is the death knell to collaborative modern teams. Who the f wants to waste their day with that UX and feature set?
- DaiPlusPlus 3y ago
  > Who the f wants to waste their day with that UX and feature set? TFS' UX is hardly any worse than Jira's. BTW, if your complaint is based on your personal experience dealing with hideously complex Issue/Bug form-fields, "areas", and the like, then that's not so-much an issue with TFS/AzureDevOps, but with your PMs, who are the ones responsible for applying customizations to the built-in workflow forms. The stock workflow forms/fields are a (relative) breeze to use compared to Jira, IMO (but GitHub Issues+Projects are better, I agree).
- datadrivenangel 3y ago
  ADO makes me yearn for Jira because of how slow and clunky it is.
  - twisteriffic 3y ago
    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.
WorldMaker 3y ago
If you have access to Azure DevOps Server your company likely also has access in its existing plans to GitHub Enterprise (on-prem) as well. GitHub Enterprise is usually about 6 to 9 months behind GitHub "Regular", but that's quite a bit better than Azure DevOps "Regular" which now seems destined to be 2-3 years behind GitHub and however far Azure DevOps Server trails behind that. Microsoft is still playing "will they/won't they" with killing Azure DevOps for whatever reasons make sense mostly only to themselves, but it is hard not to wonder if the writing is on the wall to migrate to something like GitHub Enterprise sooner rather than later. (Arguably yes, running GHE is different than Azure DevOps Server, as it is still mostly not Microsoft-stack. But I'm told they package it in a friendly enough way that even companies deep in Microsoft-stack-only don't have too many problems.)
- TheNewsIsHere 3y ago
  I keep hearing rumors that I can’t corroborate that the decision has already been made to kill Azure DevOps but that there won’t be an announcement until there’s a timeline. I’ve never seen it in black and white. I’ve seen that comment several times on HN, but it’s always so couched that it’s sort of useless. It seems like one of those rumors that doesn’t die, and then just becomes self-fulfilling if they ever do announce it.
  - WorldMaker 3y ago
    Microsoft's "on the record" voice is always "Azure DevOps is alive and has an active roadmap". You can read that roadmap for yourself. It is kept in a GitHub repository. Last time I checked this year the last commit was sometime in 2020. The last group of features that loudly launched for Azure DevOps were branded "GitHub Advanced Security for Azure DevOps". (This is where I get the 2-3 years behind GitHub metric.) Microsoft's actions seem to be speaking a lot louder than their "on the record" words. I've heard from multiple "off the record" sources who are entirely hearsay and I cannot name names that "Yes, of course Azure DevOps is dead." The best, I can say, as mostly an outsider is that Azure DevOps is at least "undead" and definitely in some sort of zombie state. I've got an unsubstantiated feeling, again as mostly an outsider, that Microsoft is somehow superstitious about Azure DevOps' home office (Microsoft office in North Carolina was founded out of Microsoft's source control dreams) and is afraid to kill it.

whoopsie 3y ago

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

DaiPlusPlus 3y ago
> Who the f wants to waste their day with that UX and feature set? TFS' UX is hardly any worse than Jira's. BTW, if your complaint is based on your personal experience dealing with hideously complex Issue/Bug form-fields, "areas", and the like, then that's not so-much an issue with TFS/AzureDevOps, but with your PMs, who are the ones responsible for applying customizations to the built-in workflow forms. The stock workflow forms/fields are a (relative) breeze to use compared to Jira, IMO (but GitHub Issues+Projects are better, I agree).
datadrivenangel 3y ago
ADO makes me yearn for Jira because of how slow and clunky it is.
- twisteriffic 3y ago
  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.

WorldMaker 3y ago

If you have access to Azure DevOps Server your company likely also has access in its existing plans to GitHub Enterprise (on-prem) as well. GitHub Enterprise is usually about 6 to 9 months behind GitHub "Regular", but that's quite a bit better than Azure DevOps "Regular" which now seems destined to be 2-3 years behind GitHub and however far Azure DevOps Server trails behind that. Microsoft is still playing "will they/won't they" with killing Azure DevOps for whatever reasons make sense mostly only to themselves, but it is hard not to wonder if the writing is on the wall to migrate to something like GitHub Enterprise sooner rather than later. (Arguably yes, running GHE is different than Azure DevOps Server, as it is still mostly not Microsoft-stack. But I'm told they package it in a friendly enough way that even companies deep in Microsoft-stack-only don't have too many problems.)

TheNewsIsHere 3y ago
I keep hearing rumors that I can’t corroborate that the decision has already been made to kill Azure DevOps but that there won’t be an announcement until there’s a timeline. I’ve never seen it in black and white. I’ve seen that comment several times on HN, but it’s always so couched that it’s sort of useless. It seems like one of those rumors that doesn’t die, and then just becomes self-fulfilling if they ever do announce it.
- WorldMaker 3y ago
  Microsoft's "on the record" voice is always "Azure DevOps is alive and has an active roadmap". You can read that roadmap for yourself. It is kept in a GitHub repository. Last time I checked this year the last commit was sometime in 2020. The last group of features that loudly launched for Azure DevOps were branded "GitHub Advanced Security for Azure DevOps". (This is where I get the 2-3 years behind GitHub metric.) Microsoft's actions seem to be speaking a lot louder than their "on the record" words. I've heard from multiple "off the record" sources who are entirely hearsay and I cannot name names that "Yes, of course Azure DevOps is dead." The best, I can say, as mostly an outsider is that Azure DevOps is at least "undead" and definitely in some sort of zombie state. I've got an unsubstantiated feeling, again as mostly an outsider, that Microsoft is somehow superstitious about Azure DevOps' home office (Microsoft office in North Carolina was founded out of Microsoft's source control dreams) and is afraid to kill it.