The document discusses new possibilities for integrating DevOps initiatives with Team Foundation Server (TFS) through extensions. It covers customizing and configuring TFS/VSTS, extending functionality through extensions in the marketplace, and integrating other tools. Examples of extensions are provided for managing requirements with a custom hub and adding build tasks for legacy systems. The process for creating an extension, packaging it, publishing it, and making it public is also outlined.
The Ultimate Test Automation Guide_ Best Practices and Tips.pdf
TFS Extensions: Novas possibilidades para integrar suas iniciativas de DevOps ao TFS
1. Globalcode – Open4education
Trilha – DevOps .Net
TFS Extensions
Novas possibilidades para integrar suas iniciativas de DevOps ao TFS
Igor Rosa Macedo
2. Globalcode – Open4education
Agenda
DevOps: Porque ferramentas flexíveis são importantes
para DevOps?
Conceito: Customização/Configuração, Integração e
Extensão
TFS/VSTS: possibilidades antes das extensões
TFS/VSTS: novas possibilidades
Marketplace
Extensões e integrações
Cenários de aplicação:
Gestão de Demandas: Custom Hub
Build VS2003: Build Task
Passo a passo: criando uma extensão:
21. Globalcode – Open4education
VSTS/TFS Extensions
An integration is a product, tool, or service that
integrations with a Microsoft product in some way,
but does not install into that Microsoft product
directly.
30. Globalcode – Open4education
Pontos de Extensão
Workitem form
• Add a group to the main page
• Add a page (tab)
• Add an action to the context menu
• Listen for events on the form
41. Globalcode – Open4education
Armazenamento de dados
Settings: simple key-value
settings (like user
preferences)
Documents: collections of
similar complex objects
(documents)
45. Globalcode – Open4education
Tornando Público
“Send an email to vsmarketplace@microsoft.com
•Use the subject Publisher verification request
•Include your publisher ID in the e-mail
•Send from your organization/company e-mail address
•Share details of your association with a business/company and other
information such as
•Link to your site
•Link to your LinkedIn account
•Link to your GitHub account
•Link to your blog
•Share details about your extension/integration
•Microsoft will respond within 2 business days”
• Verificação do publisher