71–80 of 92 posts
Earlier quoted context omitted.
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)
Hah, long time TFS and VSTS user here - I recently got so annoyed with colleagues mis-using these acronymns that I sent out an email with a glossary of terms for TFS, VSTS, TFVC, VSO etc :)
Earlier quoted context omitted.
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…
Another (mostly) happy VSTS user here, also loving the CI/CD functionality. 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 t…
For outages, you can subscribe at https://blogs.msdn.microsoft.com/vsoservice (in the toolbar on the right hand side). We don't send out email notifications without you opting in, nor will we, but we do have some ideas to improve the way we notify people that we're working on.
And as for build agents, we're working on that, especially around the caching. Appreciate all the feedback.
Earlier quoted context omitted.
Just drop the "dev" and call it AzureOps. Still way less confusing than the prior branding.
AzureOps has a nice ring to it! With regards to VSTS, I probably just have a soft spot for Visual Studio itself.
The name made a lot more sense back in the day when the premier client was actually the Visual Studio IDE. But today, most people interact with Azure DevOps with their browser and too many people think "Visual Studio Team Services" is a web-based IDE.
The name change is bittersweet. We've been "Visual Studio " since the first release of our on-premises product, well over a decade ago. But I'm confident about this next phase of Azure DevOps.
Earlier quoted context omitted.
Do you happen to know where the root cause analysis will be posted if it is made public?
It will be on our service availability blog: https://blogs.msdn.microsoft.com/vsoservice/ , and I'll reply here with a direct link once it's online.
PM for Azure DevOps here. The team is really excited about this launch, and many of us are here to answer questions on Azure DevOps, or any of the individual services like Azure Pipelines, the new GitHub Marketplace app, or our free build offer for open source projects.
Hello, I think I found a bug with your organizations. I own skmexyz.visualstudio.com (under sk@skme.xyz account) and I tried to transfer it to skmexyz@skmexyz.onmicrosoft.com and now: 1. Both accounts are not admins so I can't delete / modify it (it asks me to contact the administrator when I am obviously the administrator) 2. It claims that it's being managed by Default Directory on Azure but I can't appear do anyth…
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.
* Pipelines is a stand-alone service that can be acquired and used separately
* Pipelines can be directly acquired and configured from the GitHub marketplace
* Pipelines is effectively free to use for open source
* Pipelines free limits have been significantly increased for private projects
* Other Azure DevOps services (e.g. Boards) can now be used separately, too
Earlier quoted context omitted.
AzureOps has a nice ring to it! With regards to VSTS, I probably just have a soft spot for Visual Studio itself.
I love Visual Studio, but the product currently known as Azure DevOps (formerly known as VSTS) really has nothing to do with Visual Studio. The name made a lot more sense back in the day when the premier client was actually the Visual Studio IDE. But today, most people interact with Azure DevOps with their browser and too many people think "Visual Studio Team Services" is a web-based IDE. The name change is bitterswe…
The term "DevOps" is now meaningless. The search for a new short term to describe "operations and development teams working together using high quality software tools to define, automate and distribute configuration and management information, integrating QA, release management and security" has begun.
I gave myself a title at my last job that more accurately reflected the nature of the work - Senior Software Therapist. You get what you put into it, hopefully you don’t need the person for long, but most people that start it will probably not listen to the therapist and stay in treatment for longer. If your software and organization building and running it works 100% fine then you don’t need the therapist. I have no…
Can MSDN subscribers apply their credit towards this service?
Azure DevOps is free for teams of up to five users. It's also effectively free for open source use by teams of any size. Larger teams working on private projects would need to be on one of the paid tiers and can't use the free Azure credits to pay for that.