O vídeo já está público no YouTube, no Canal .Net:

As referências da minha palestra

• Docker for Windows
  • https://docs.docker.com/engine/installation/windows/
• Docker Machine
  • https://docs.docker.com/machine/overview/
• Visual Studio Tools for Docker
  • https://marketplace.visualstudio.com/items?itemName=MicrosoftCloudExplorer.VisualStudioToolsforDocker-Preview
• Docker Integration for VSTS
  • https://marketplace.visualstudio.com/items?itemName=ms-vscs-rm.docker
• Building .NET Core Linux Docker Images with Visual Studio Team Services
  • https://blogs.msdn.microsoft.com/stevelasker/2016/06/13/building-net-core-linux-docker-images-with-visual-studio-team-services/
• Docker VSTS Agent image
  • https://hub.docker.com/r/microsoft/vsts-agent/
• Debugging apps num Container Docker local
  • https://docs.microsoft.com/en-us/azure/vs-azure-tools-docker-edit-and-refresh
• Docker Machine e Azure Driver
  • https://docs.docker.com/machine/drivers/azure/
  • https://docs.microsoft.com/en-gb/azure/virtual-machines/virtual-machines-linux-docker-machine
• Microsoft SQL Server no Linux em um Container Docker
  • https://aka.ms/mssqllinuxdocker
• Visual Studio Team Services em vídeos: VSTS Sprints
  • https://www.youtube.com/canalvsosprints

The event

My session

People

Processes

Code

Deployment

• Canary Deployment: this concept is used to release a new version in production and, in case of an incident, a minimal group of user accounts, including the own team's, is impacted. Here we can conclude that YES, the team uses its own product. Dog-fooding!
  • The Canary term is based on the history of the coal miners who took a canary every time they go to the mine and, if the canary dies, it was time to leave the mine because the air was too toxic to stay there.
• Scale Units: to make Canary Deployment possible, VSTS has some Scale Units (SUs) as production environments. Each one of them is a set of Team Services accounts that, the smaller, the more early adopters they are. Scale Unit 0 is what they call Canary Instance.
  • It's possible to request to be an early adopter throught a support request to the product team. You may go from SU3 to Su2 or SU1. It never hurts to try, huh? :-) Be aware that only some internal teams, employees and initiatives are elegible to SU0.
• Release Management: And here we have another YES! The new releases of VSTS are triggered automatically on each SU through Release Management. It was so cool to talk about that. We were done with this aspect by discovering that LightRail, a PowerShell-based tool, is used in one of the few tasks to run this deployment in each environment.
• How to be up to date with the service status: at last, we saw that there's a lot of transparency about service health. It's possible to follow the detailed news and the service status through the following channels:
  • Twitter @VSTeam: news and incident announcements;
  • Product Status Website: here you can easily know if there's any problem with the product operation. And remember: green means that everything is ok; yellow means that there's a problem which the team already know the root cause and they're already working on it/the product is partially unavailable; and red means that there's a problem with an unknown root cause and the team is still investigating/the product is unavailable.
  • Service Blog: here it is possible to know details of deployments, ivestigation and correction of problems.

The Sprint 90

Dashboards

Improved pull request experience

Manual test iteration results

Retention policy for test results

Reorder and re-parent tasks from the Kanban board

Extensibility on the work item form

PREVIEW: Updates to the new work item form

• Azure Active Directory Group Support
  • You can now use the groups you defined in your Azure AD to work with permissions in VSTS.
• Starting with git, made easy
  • The team made some improvements to the first user experience with Git on VSTS.
• Improved commit details
  • The summary got better so you can now see the commit message in a better way. There's also a better way to view the diff with the parent commit
• SonarQube analysis from a Maven build task
  • After this deployment, we got a new simple checkbox on the Maven Build Task to run a SonarQube analysis
• PREVIEW: New work item form
  • A brand new Work Item experience! New layout; prepared for customization; discussion and more.

• Inline tasks on the Kanban board
  • Now you can plan the tasks of a Backlog Item directly in the Kanban board. Easy and dynamic, keep the Kanban view while planning your Sprint.
• Query and display of Kanban fields
  • Remember that new columns you could add to the Kanban View? Right, now you can query over them.
• Multi-select items on the backlog
  • If you want to perform actions in multiple items of your backlog, just select all of them and do it!
• Branch policy to require linked work items
  • Yep. Now you can configure this policy for branches in Pull Request of a Git repository.
• Export test outcomes
  • There were already some stuff you could export from tests in VSTS. You can now export the Test Outcomes either, which allows you to have more information about the test execution. Take a look.
• Work item trend and rollup reporting in Power BI
  • Great! The integration between VSTS and the Power BI is now live for Work Item reports.
• Support for publishing xUnit results
  • One more testing framework you can use in your builds and export the test results using the Publish Test Results task: xUnit!

O Premier Field Engineer

• Proativas: assessments, ações preventivas, health checks, chalk & talks, workshops, Programas de Gerenciamento de Risco, Revisões de Suportabilidade, entre outros;
• Reativas: troubleshooting, disaster recovers, suporte à situações críticas, entre muitas outras possibilidades também. Isto sem contar a gestão do cliente durante uma eventual situação difícil.

O Time

O Ramp Up