1 / 12

Southworks Induction Program Build Server Exercise

Southworks Induction Program Build Server Exercise. Exercise Focus. Target Level: Leader (Ranger) Assess technical skills Assess Communication skills Assess behaviours related to Work estimation and planning Deal with Ambiguity Change management Learn new technologies.

marvel
Download Presentation

Southworks Induction Program Build Server Exercise

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Southworks Induction ProgramBuild Server Exercise

  2. Exercise Focus • Target Level: Leader (Ranger) • Assess technical skills • Assess Communication skills • Assess behaviours related to • Work estimation and planning • Deal with Ambiguity • Change management • Learn new technologies

  3. DPE Assets Generation Process 1 2 3 • Coding • Defining Dependencies • Writing • Styling • Validating • Defining Metadata • Transforming • Validating • Uploading to ms.com • Uploading to MSDN • Uploading to ? • Publishing • Authoring • Packaging 4 5 • Downloading • Dependency Checking • Learning • Stats Analysis (Downloads, etc.) • Consuming • Analizing

  4. Current Processes TFS DPE Make corrections, small changes doc T4 C# Produce docs, code Other Vendors Navigation Templates Documents Source Code Package sent to the customer Produce docs, code and templates Southworks PowerShell CmdLets Package Creation Run scripts, generate package Msdn.com SFX * Training Kit Packages * MSDN Training Course * Samples

  5. Problems with current process • DPE Evangelists wants to have a package and publish to MSDN at any time, not depend on Southworks to do that • Multiple packages might be built at the same time • The process of creating a package and upload it to the Download Center is cumbersome we need guidance for evangelists who don’t know the process

  6. What are theissuestoday in eachstage of theprocess?

  7. Issues in Authoring Stage • Lack of knowledge on how to get DocTools • Lack of knowledge on how to use DocTools & styles • Lack of awareness of validation tools • The default writing experience generates tons of issues with the conversion • Validation tools does not have all the rules • VSI generation is manual process and often is skipped leading to wrong code snippets • VSI in 2010 does not work properly and it doesn’t work with phone tools • Lack of knowledge on how to generate dependency checker manifest • Lack of knowledge of the process to generate a new version of a lab

  8. Issues in Packaging Stage • Build Server & ECF performance (220mb package 1hr to build) • Build Server does not scale reliably (cannot run more than one build at a time) • Usage of Word Interop is fragile (hangs the process) • Metadata generation is a manual task prone to error • Lack of knowledge of the process to generate a new version of a lab - poor versioning scheme for the content • Lack of knowledge on how to troubleshoot issues during the packaging process • Metadata of shared labs across TKs is not easy to manage • Notifications are hard – when build is completed • Continous integration – continous validation & automated builds • SCM management issues – syncronization, mostly metadata

  9. Issues in Publishing Stage • MSDN service is slow and we are not handling it gracefully (connectivity is an issue and error msgs are meaningless) • MSDN only works on corpnet and with Joni credentials • Lack of knowledge on how to troubleshoot issues during the publishing process • The service is very old – only 1 guy knows it

  10. Issues in Consuming Stage • Dependency checking sometimes fail • Lack of formal triage of issues that came from the field • The delivery model – how do we get updated HOLs in VMs (for workshops). Distribution and refresehs is challenging. Streamline distribution model. Notify updates.

  11. Issues in Analizing Stage • Lack of a centralized information repository for all DPE assets • EDS not being used, not easy to use? • Lack of a tool to review a training content • Provide data about content we produce – how many hols, present, filter by technology, etc. Reporting in gral is hard • Reporting based on the metrics – what impact a content is having • Screen crapping – aggregate of all the data out there in the web • Planning & status tracking – where we are with certain content? Priorities, etc.

  12. Ask • Propose an architecture for the build server and present it • Use Azure so it can be easily scaled and it’s an opportunity for DPE to showcase the platform in a real-world project • Make a demo of the proposed architecture • Create a ballpark estimate in # of iterations that it will take to build it • Propose a roadmap for next steps (long term)

More Related