For many of us in the northern hemisphere, things are really heating up — both the temperature and the move into DevOps in the cloud. This week we saw some great posts on DevOps adoption, including cloud migration,
As promised in the Protecting our users from the ESLint NPM package breach blog post last week, we have deployed new REST APIs to allow administrators of Visual Studio Team Services (VSTS) accounts to centrally revoke Personal Access Tokens (PAT) and JSON Web Tokens (JWT) created by users in their accounts.
This week I’ve been busy talking with Open Source developers and users at OSCON, explaining how VSTS can enable their builds with our hosted (or on-premises!) build agents. Meanwhile, we’ve seen some incredible podcasts and blog posts about DevOps in Azure.
In our interactions with users, we see a lot of confusion over the word account. Currently we use account to mean things like https://contoso.visualstudio.com and things like firstname.lastname@example.org. To avoid this confusion, and to better align with the terminology of the broader developer and OSS community,
We’re excited to announce updates to the new dashboard experience. This new experience lets you:
- Easily switch between your team’s dashboards
- Fine tune team permissions on individual dashboards
- Find and favorite the dashboards you need
It is now generally available for VSTS customers and coming to TFS in the next major version.
On the 12th of July 2018, malicious code was detected in two popular open-source NPM packages, eslint-scope (version 3.7.2) and eslint-config-eslint (version 5.0.2). As a result, developers who downloaded and installed these packages may have had credentials stored in their .npmrc file compromised.
It’s been another busy week for VSTS and DevOps, and we’re excited to see some interesting articles and podcasts about DevOps on Azure.
Moving a Git Repo from Bitbucket to VSTS
One of the great things about Git is that it’s easy to move your repository from one hosting provider to another –