Codecov.io added tokenless uploading of coverage results for public Azure Pipelines.
Post by this author
Azure Pipelines has supported container jobs for a while now. You craft a container with exactly the versions of exactly the tools you need, and we'll run your pipeline steps inside that container. Recently we expanded our container support to include service containers: additional, helper containers accessible to your pipeline.
Forks – the ability to create a server-side copy of a Git repository – is rolling out across Visual Studio Team Services (VSTS) and available in TFS 2018 RC1 as a public preview. In VSTS, you won’t have to do anything to turn it on,
The VSTS platform offers a security REST endpoint which allows you to add and remove permissions on resources. (To understand the rest of this blog post, you’re going to want to skim those docs first.) Several of the security APIs, as well as TFSSecurity.exe,
Like everything in VSTS and TFS, Git repos are protected by a set of permissions. For instance, you must have Read for a repo to clone or view its contents. Likewise, you must have Contribute to push changes. Until recently, you needed one permission to create,
We’ve had a handful of support calls lately from customers who deleted their team project folder in TFVC. tf.exe makes it easy to do, but not easy to undo. Fortunately, the fix is straightforward, and Will Lennon has written it up in a blog post.
New features and UI changes naturally get a lot of attention. Today, I want to spotlight the less visible work that we do on Team Services: ensuring our performance and scale meet our customers’ needs now and in the future. We are constantly working behind the scenes profiling,
This is the third and final post in a series covering strategies for versioning a NuGet package. If you missed part 1 or part 2, you should read those first. Today’s post walks through a specific workflow that Git users could adopt,
This is part 2 in a series of blog posts covering strategies for versioning a NuGet package. If you missed part 1, pick it up here. Today’s post talks about future improvements we’d like to make to the versioning and releasing flows.
On the Package Management team, we’re frequently asked how to think about versioning packages. Conceptually, it’s simple: NuGet (like many package managers) prefers semantic versioning (SemVer), which describes a release in terms of its backwards-compatibility with the last release. But for teams that have adopted continuous delivery,