51–60 of 92 posts
But this looks like they've just changed the URL and stuck the name "Azure DevOps" onto the VSTS site? Even the pricing and plans seem to be the same - I really don't get how they're talking like they're launching something new, rather than just having a rebranding exercise after buying GitHub.
1. Team Foundation Server (TFS)
2. Visual Studio Team Services (VSTS)
3. Azure DevOps
Imagine if GitHub renamed itself every few years?
Or is the idea that this is going to be marketed towards Azure users and GitHub will be promoted to the new VSTS once it gets a few more features for project management and PRs?
Earlier quoted context omitted.
PM for Azure DevOps here (formerly VSTS). It is a rebranding, but it's more than merely a rebranding. We're breaking out the individual services so that they're easier to adopt. For example, if you're just interested in pipelines, you can adopt only pipelines. We've got some neat new features launching today and more coming soon. My favorite new feature is the Azure Pipelines app the the GitHub Marketplace. It makes…
We are considering using TFS (now Azure DevOps Server) for CI/CD of database related projects. Curious, how does DevOps handle SQL Database, SSIS, SSRS and SSAS visual studio projects when it comes to CI/CD? We have a custom solution currently in place, but would like to simplify this if possible.
I wonder if Azure DevOps will have a day long outage like VSTS had last week? That had a legitimately productivity cost to a lot of companies, and the more vested in the VSTS toolchain you were the harder hit you were. I'm legitimately surprised they're launching this so soon after that, particularly considering there's been no real post-mortem, and no update on how they'll stop this happening again. "It is Azure's f…
I certainly hope not. I'm not going to argue that this was anything but a disappointment to our customers - and one that we're eager to prevent from happening again. But we have never said that this was Azure's fault. It wasn't. We've put the blame where it belongs: on us. We're nearly done writing up the root cause analysis and an analysis of our next steps to prevent this from happening in the future.
Now, what I hated the most about this was the communication - there wasn't any. Why not email impacted users to let them know you're aware and working on a fix?
Earlier quoted context omitted.
I certainly hope not. I'm not going to argue that this was anything but a disappointment to our customers - and one that we're eager to prevent from happening again. But we have never said that this was Azure's fault. It wasn't. We've put the blame where it belongs: on us. We're nearly done writing up the root cause analysis and an analysis of our next steps to prevent this from happening in the future.
3 weeks ago there was a different outage that meant no hosted build agents were working in the west europe region, and it lasted for more than 24 hours. Now, what I hated the most about this was the communication - there wasn't any. Why not email impacted users to let them know you're aware and working on a fix?
I've been using VSTS (Visual Studio Team Services) for a few years now, and I think it's great. But this looks like they've just changed the URL and stuck the name "Azure DevOps" onto the VSTS site? Even the pricing and plans seem to be the same - I really don't get how they're talking like they're launching something new, rather than just having a rebranding exercise after buying GitHub.
Although there have been slight tweaks and UI/UX updates.
Still no Mercurial. yawn Really sucks to see Microsoft giving up on us Hg users, considering it was the only viable DVCS on windows for years until people finally got git working with a bunch of issues.
Earlier quoted context omitted.
PM for Azure DevOps here (formerly VSTS). It is a rebranding, but it's more than merely a rebranding. We're breaking out the individual services so that they're easier to adopt. For example, if you're just interested in pipelines, you can adopt only pipelines. We've got some neat new features launching today and more coming soon. My favorite new feature is the Azure Pipelines app the the GitHub Marketplace. It makes…
As a mostly very satisfied user, I gotta say, y'all have a great product. The CI/CD part of VSTS (I like the old name better :P) is killer and by far my favorite platform to use now. However, I've had my builds break twice out of nowhere with no recourse other than submitting a forum post and hoping someone gets back to me in a reasonable amount of time. I can't imagine going back to another platform, but its really…
I too have had builds break recently out of nowhere:
1. Related to NPM being upgraded on the hosted agent, which was fixed easily enough (after trawling through logs) by forcing the task to use an older version
2. SQL LocalDB connections stopped working, so integration tests couldn't run - this lasted for around 2 weeks!
I also ended up on the Microsoft support forums... unfortunately, responses on those forums from Microsoft staff are invariably late and of infuriatingly poor quality.
I ended up on the VSTS Agent image GitHub site instead, and raising an issue there was far more helpful.
VSTS is a great product, I just really wish there was a decent support option for when things go wrong.
I also wish Microsoft would actively communicate with impacted customers to notify them where there are outages.
Oh, and I wish the hosted build agents ran on better hardware - they are slow, even compared to the smaller Azure VMs. For example, we have a build that takes 14 minutes on the (paid) hosted agent, or 3 minutes on a B2ms Azure VM. Some of that is down to NPM and Nuget package caching, but even the actual msbuild and test stages are much slower.
Is this just a rebranding? As a long time user of VSTS, I am failing to see how Azure DevOps is different from VSTS. Boards, CI/CD, testing - that's already part of VSTS, and has been for quite some time. Is Microsoft just rebranding for keyword searching or something? Or are there actual technical changes / new features that are being introduced?
This is a rebranding yes. VSTS was a bad name that confused potential customers because they thought of the IDE, and so no one really knew what the product was from the name alone. (Work on VSTS team)
Earlier quoted context omitted.
it looks like rebrand + redesign + decoupling the individual services so they're easier to adopt independently?
Yes that's right + free pipeline for OSS project. From: PM for Azure DevOps here (formerly VSTS)
I'm nitpicking though, and I have to say, 10 concurrent jobs and unlimited build time is really generous.