DOCSLIB.ORG

Azure Boards the Other Side of Devops

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Azure Boards the Other Side of Devops Azure Boards The Other Side of DevOps Presented by: Tricia Sinclair • Twitter: @tassyja • Linkedin: triciasinclair • Blog: www.triciasinclair.com • Hashtags Social • #msdyn365 #d365ug • https://d365ug.com/uk • https://www.youtube.com/c/D365UGUK Agenda Azure DevOps Overview Dive Into Azure Boards Feature Demonstration Useful Tools and Techniques Azure DevOps Also Known As: Visual Studio 2005 Team System Visual Studio Team System 2008 Team Foundation Server 2010 Visual Studio Online Visual Studio Team Services Azure DevOps Azure DevOps Server “DevOps is the union of people, process and technology to enable continuous delivery of value to customers” - Donovan Brown (Principal DevOps Manager @ Microsoft) Overview of Azure DevOps Azure Boards • Work Item Management Plan • Alerts • Dashboards • Manage Feedback • Delivery Plans • Boards Feedback Overview of Azure DevOps Azure Boards Plan • Team Foundation Version Control • GIT Azure Repos Build • Code Reviews • Code Searches Feedback Overview of Azure DevOps Azure Boards Plan • Continuous Integration • Continuous Deployment Azure Repos Build • Release Approvals Azure Test Pipelines Deploy Feedback Overview of Azure DevOps Plan Azure Boards • Package Management Build Azure Repos Azure Test Pipelines Azure Deploy Artifacts Feedback Overview of Azure DevOps Azure Boards Plan Azure Repos • Test Plan Management Build • Test Reporting Azure Test Pipelines Azure Deploy Artefacts Azure Test Feedback Plans Overview of Azure DevOps Plan Feedback Build Deploy Test MANAGING WORK ITEMS Demo Azure DevOps: Work Items Creating Requirements in Azure DevOps Azure DevOps Create requirements using requirement work item form in Azure DevOps. Microsoft Excel Use the Office 365 team explorer integration to create work items in Excel and publish to Azure DevOps Power Automate Create a flow triggered from PSA to create work items in Azure DevOps from project tasks via the Azure DevOps Flow connector Github Action Trigger an action to be run automatically or manually to push issues to Azure Boards LCS Create user stories or requirements in Azure DevOps from the Business Process Modeller in D365 Finance and Operations Azure DevOps: Work Items Creating Requirements in Azure DevOps Azure DevOps Create requirements using requirement work item form in Azure DevOps. Microsoft Excel Use the Office 365 team explorer integration to create work items in Excel and publish to Azure DevOps Power Automate Create a flow triggered from PSA to create work items in Azure DevOps from project tasks via the Azure DevOps Flow connector Github Action Trigger an action to be run automatically or manually to push issues to Azure Boards LCS Create user stories or requirements in Azure DevOps from the Business Process Modeller in D365 Finance and Operations Azure DevOps: Work Items Creating Requirements in Azure DevOps Azure DevOps Create requirements using requirement workCreating item Requirements in Azure DevOps form in Azure DevOps. Microsoft Excel Use the Office 365 team explorer integration to create work items in Excel and publish to Azure DevOps Power Automate Create a flow triggered from PSA to create work items in Azure DevOps from project tasks via the Azure DevOps Flow connector Github Action Trigger an action to be run automatically or manually to push issues to Azure Boards LCS Create user stories or requirements in Azure DevOps from the Business Process Modeller in D365 Finance and Operations Azure DevOps: Work Items Creating Requirements in Azure DevOps Azure DevOps Create requirements using requirement workCreating item Requirements in Azure DevOps form in Azure DevOps. Microsoft Excel Use the Office 365 team explorer integration to create work items in Excel and publish to Azure DevOps Power Automate Create a flow triggered from PSA to create work items in Azure DevOps from project tasks via the Azure DevOps Flow connector Github Action Trigger an action to be run automatically or manually to push issues to Azure Boards LCS Create user stories or requirements in Azure DevOps from the Business Process Modeller in D365 Finance and Operations Supports the Scrum Scrum methodology as defined by the Scrum Organisation Agile Supports Agile planning Azure methods (including Scrum) DevOps Capability Maturity Model Processes Integration supports CMMI formal waterfall methodology Basic Tied to no methodology. Slack Integration: https://marketplace.visualstudio.com/items?itemName=ms-vsts.vss-services-slack Analytics: https://marketplace.visualstudio.com/items?itemName=ms.vss-analytics Delivery Plans: https://marketplace.visualstudio.com/items?itemName=ms.vss-plans Useful Tools Sprint Drop Plan: https://marketplace.visualstudio.com/items?itemName=yanivsegev.Drop-plan-extension and Retrospective: https://marketplace.visualstudio.com/items?itemName=ms-devlabs.team-retrospectives Extensions Work Item Visualiser: https://marketplace.visualstudio.com/items?itemName=ms-devlabs.WorkItemVisualization Estimate: https://marketplace.visualstudio.com/items?itemName=ms-devlabs.estimate Power Automate: https://marketplace.visualstudio.com/items?itemName=MS-Flow.microsoftflow Feedback Client: https://www.microsoft.com/en-us/download/details.aspx?id=48142 Team Explorer: https://go.microsoft.com/fwlink/?LinkId=691127 Questions? • Twitter: @tassyja • Linkedin: triciasinclair • Blog: www.triciasinclair.com • Hashtags Social • #msdyn365 #d365ug • https://d365ug.com/uk • https://www.youtube.com/c/D365UGUK Thank You.
Load more

Recommended publications
  • Pragmatic Version Control Using Subversion
    What readers are saying about Pragmatic Version Control using Subversion I expected a lot, but you surprised me with even more. Hav- ing used CVS for years I hesitated to try Subversion until now, although I knew it would solve many of the shortcom- ings of CVS. After reading your book, my excuses to stay with CVS disappeared. Oh, and coming from the Pragmatic Bookshelf this book is fun to read too. Thanks Mike. Steffen Gemkow Managing Director, ObjectFab GmbH I’m a long-time user of CVS and I’ve been skeptical of Sub- version, wondering if it would ever be “ready for prime time.” Until now. Thanks to Mike Mason for writing a clear, con- cise, gentle introduction to this new tool. After reading this book, I’m actually excited about the possibilities for version control that Subversion brings to the table. David Rupp Senior Software Engineer, Great-West Life & Annuity This was exactly the Subversion book I was waiting for. As a long-time Perforce and CVS user and administrator, and in my role as an agile tools coach, I wanted a compact book that told me just what I needed to know. This is it. Within a couple of hours I was up and running against remote Subversion servers, and setting up my own local servers too. Mike uses a lot of command-line examples to guide the reader, and as a Windows user I was worried at first. My fears were unfounded though—Mike’s examples were so clear that I think I’ll stick to using the command line from now on! I thoroughly recommend this book to anyone getting started using or administering Subversion.
    [Show full text]
  • Azure Devops Server (TFS) Integration with JIRA and Github
    DATASHEET Azure DevOps Server (TFS) Integration with JIRA and GitHub The integration of Azure DevOps Server (TFS) with JIRA and GitHub ensures completely traceability of all workitems in the ecosystem. With this integration, the product management team will have real-time visibility into all defects, commit trends, and commit volume. Integration overview In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements. Best-of-breed systems such as Azure DevOps Server (TFS), JIRA, and GitHub bring rich functionalities to the ecosystem. By integrating Azure DevOps Server (TFS), JIRA, and GitHub, the product development team will have real-time visibility into the defects logged by QA team and commits made by the development team. It is also easier for product development team to enforce authentic commits against each work item, and access the changes/edits made to the commits files. How Azure DevOps Server (TFS) - JIRA - GitHub integration is beneficial for an enterprise With Azure DevOps Server (TFS) + JIRA + GitHub integration, enterprises can: Track commit volume, track commit trends and edits/changes to commit files in real time Make better and faster decisions Enforce authentic commits to make sure each commit is Ensure complete traceability of a happening against a scheduled and open workitem ‘requirement’ Eliminate manual effort to close JIRA or Azure DevOps Server (TFS) Meet all compliance requirements workitems by automating the state transition on GitHub commit Ensure quality delivery in stipulated time Leverage the best of functionality and How OpsHub Integration Manager integrates Azure collaboration in the delivery ecosystem DevOps Server (TFS), JIRA, and GitHub OpsHub Integration Manager integrates Azure DevOps Server (TFS), JIRA, and GitHub - all systems with each other bi-directionally.
    [Show full text]
  • Version Control 101 Exported from Please Visit the Link for the Latest Version and the Best Typesetting
    Version Control 101 Exported from http://cepsltb4.curent.utk.edu/wiki/efficiency/vcs, please visit the link for the latest version and the best typesetting. Version Control 101 is created in the hope to minimize the regret from lost files or untracked changes. There are two things I regret. I should have learned Python instead of MATLAB, and I should have learned version control earlier. Version control is like a time machine. It allows you to go back in time and find out history files. You might have heard of GitHub and Git and probably how steep the learning curve is. Version control is not just Git. Dropbox can do version control as well, for a limited time. This tutorial will get you started with some version control concepts from Dropbox to Git for your needs. More importantly, some general rules are suggested to minimize the chance of file losses. Contents Version Control 101 .............................................................................................................................. 1 General Rules ................................................................................................................................... 2 Version Control for Files ................................................................................................................... 2 DropBox or Google Drive ............................................................................................................. 2 Version Control on Confluence ...................................................................................................
    [Show full text]
  • Generating Commit Messages from Git Diffs
    Generating Commit Messages from Git Diffs Sven van Hal Mathieu Post Kasper Wendel Delft University of Technology Delft University of Technology Delft University of Technology [email protected] [email protected] [email protected] ABSTRACT be exploited by machine learning. The hypothesis is that methods Commit messages aid developers in their understanding of a con- based on machine learning, given enough training data, are able tinuously evolving codebase. However, developers not always doc- to extract more contextual information and latent factors about ument code changes properly. Automatically generating commit the why of a change. Furthermore, Allamanis et al. [1] state that messages would relieve this burden on developers. source code is “a form of human communication [and] has similar Recently, a number of different works have demonstrated the statistical properties to natural language corpora”. Following the feasibility of using methods from neural machine translation to success of (deep) machine learning in the field of natural language generate commit messages. This work aims to reproduce a promi- processing, neural networks seem promising for automated commit nent research paper in this field, as well as attempt to improve upon message generation as well. their results by proposing a novel preprocessing technique. Jiang et al. [12] have demonstrated that generating commit mes- A reproduction of the reference neural machine translation sages with neural networks is feasible. This work aims to reproduce model was able to achieve slightly better results on the same dataset. the results from [12] on the same and a different dataset. Addition- When applying more rigorous preprocessing, however, the per- ally, efforts are made to improve upon these results by applying a formance dropped significantly.
    [Show full text]
  • Introduction to Version Control with Git
    Warwick Research Software Engineering Introduction to Version Control with Git H. Ratcliffe and C.S. Brady Senior Research Software Engineers \The Angry Penguin", used under creative commons licence from Swantje Hess and Jannis Pohlmann. March 12, 2018 Contents 1 About these Notes1 2 Introduction to Version Control2 3 Basic Version Control with Git4 4 Releases and Versioning 11 Glossary 14 1 About these Notes These notes were written by H Ratcliffe and C S Brady, both Senior Research Software Engineers in the Scientific Computing Research Technology Platform at the University of Warwick for a series of Workshops first run in December 2017 at the University of Warwick. This document contains notes for a half-day session on version control, an essential part of the life of a software developer. This work, except where otherwise noted, is licensed under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International Li- cense. To view a copy of this license, visit http://creativecommons.org/ licenses/by-nc-nd/4.0/. The notes may redistributed freely with attribution, but may not be used for commercial purposes nor altered or modified. The Angry Penguin and other reproduced material, is clearly marked in the text and is not included in this declaration. The notes were typeset in LATEXby H Ratcliffe. Errors can be reported to [email protected] 1.1 Other Useful Information Throughout these notes, we present snippets of code and pseudocode, in particular snippets of commands for shell, make, or git. These often contain parts which you should substitute with the relevant text you want to use.
    [Show full text]
  • Microservices and Monorepos
    Microservices and Monorepos Match made in heaven? Sven Erik Knop, Perforce Software Overview . Microservices refresher . Microservices and versioning . What are Monorepos and why use them? . These two concepts seem to contradict – why mix them together? . The magic of narrow cloning . A match made in heaven! 2 Why Microservices? . Monolithic approach: App 3 Database Microservices approach . Individual Services 4 DB DB Database Versioning Microservices . Code . Executables and Containers . Configuration . Natural choice: individual repositories for each service Git . But: • Security • Visibility • Refactoring • Single change id to rule them all? 5 Monorepo . Why would you use a monorepo? . Who is using monorepos? . How would you use a monorepo? 6 Monorepos: Why would you do this? . Single Source of Truth for all projects . Simplified security . Configuration and Refactoring across entire application . Single change id across all projects . Examples: • Google, Facebook, Twitter, Salesforce, ... 7 Single change across projects change 314156 8 Monorepos: Antipatterns User workspace User workspace 9 Monorepos – view mapping User workspace . Map one or more services . Users only access files they need . Simplified pushing of changes 10 What does this have to do with Git? . Git does not support Monorepos • Limitations on number and size of files, history, contributing users • Companies have tried and failed . Android source spread over a thousand Git repositories • Requires repo and gerrit to work with 11 How can we square this circle? https://en.wikipedia.org/wiki/Squaring_the_circle 12 Narrow cloning! . Clone individual projects/services . Clone a group of projects into a single repo 13 Working with narrowly cloned repos . Users work normally in Git . Fetch and push changes from and to monorepo .
    [Show full text]
  • Higher Inductive Types (Hits) Are a New Type Former!
    Git as a HIT Dan Licata Wesleyan University 1 1 Darcs Git as a HIT Dan Licata Wesleyan University 1 1 HITs 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory But they have many other applications, including some programming ones! 2 Generator for 2 equality of equality Patches Patch a a 2c2 diff b d = < b c c --- > d 3 3 id a a b b
    [Show full text]
  • Homework 0: Account Setup for Course and Cloud FPGA Intro Questions
    Cloud FPGA Homework 0 Fall 2019 Homework 0 Jakub Szefer 2019/10/20 Please follow the three setup sections to create BitBucket git repository, install LATEX tools or setup Overleaf account, and get access to the course's git repository. Once you have these done, answer the questions that follow. Submit your solutions as a single PDF file generated from a template; more information is at end in the Submission Instructions section. Setup BitBucket git Repository This course will use git repositories for code development. Each student should setup a free BitBucket (https://bitbucket.org) account and create a git repository for the course. Please make the repository private and give WRITE access to your instructor ([email protected]). Please send the URL address of the repository to the instructor by e-mail. Make sure there is a README:md file in the repository (access to the repository will be tested by a script that tries to download the README:md from the repository address you share). Also, if you are using a Apple computer, please add :gitignore file which contains one line: :DS Store (to prevent the hidden :DS Store files from accidentally being added to the repository). If you have problems accessing BitBucket git from the command line, please see the Appendix. Setup LATEX and Overleaf Any written work (including this homework's solutions) will be submitted as PDF files generated using LATEX [1] from provided templates. Students can setup a free Overleaf (https://www. overleaf.com) account to edit LATEX files and generate PDFs online; or students can install LATEX tools on their computer.
    [Show full text]
  • Version Control – Agile Workflow with Git/Github
    Version Control – Agile Workflow with Git/GitHub 19/20 November 2019 | Guido Trensch (JSC, SimLab Neuroscience) Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich, JSC:SimLab Neuroscience 2 Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich, JSC:SimLab Neuroscience 3 Motivation • Version control is one aspect of configuration management (CM). The main CM processes are concerned with: • System building • Preparing software for releases and keeping track of system versions. • Change management • Keeping track of requests for changes, working out the costs and impact. • Release management • Preparing software for releases and keeping track of system versions. • Version control • Keep track of different versions of software components and allow independent development. [Ian Sommerville,“Software Engineering”] Forschungszentrum Jülich, JSC:SimLab Neuroscience 4 Motivation • Keep track of different versions of software components • Identify, store, organize and control revisions and access to it • Essential for the organization of multi-developer projects is independent development • Ensure that changes made by different developers do not interfere with each other • Provide strategies to solve conflicts CONFLICT Alice Bob Forschungszentrum Jülich, JSC:SimLab Neuroscience 5 Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich,
    [Show full text]
  • Distributed Revision Control with Mercurial
    Distributed revision control with Mercurial Bryan O’Sullivan Copyright c 2006, 2007 Bryan O’Sullivan. This material may be distributed only subject to the terms and conditions set forth in version 1.0 of the Open Publication License. Please refer to Appendix D for the license text. This book was prepared from rev 028543f67bea, dated 2008-08-20 15:27 -0700, using rev a58a611c320f of Mercurial. Contents Contents i Preface 2 0.1 This book is a work in progress ...................................... 2 0.2 About the examples in this book ..................................... 2 0.3 Colophon—this book is Free ....................................... 2 1 Introduction 3 1.1 About revision control .......................................... 3 1.1.1 Why use revision control? .................................... 3 1.1.2 The many names of revision control ............................... 4 1.2 A short history of revision control .................................... 4 1.3 Trends in revision control ......................................... 5 1.4 A few of the advantages of distributed revision control ......................... 5 1.4.1 Advantages for open source projects ............................... 6 1.4.2 Advantages for commercial projects ............................... 6 1.5 Why choose Mercurial? .......................................... 7 1.6 Mercurial compared with other tools ................................... 7 1.6.1 Subversion ............................................ 7 1.6.2 Git ................................................ 8 1.6.3
    [Show full text]
  • Scaling Git with Bitbucket Data Center
    Scaling Git with Bitbucket Data Center Considerations for large teams switching to Git Contents What is Git, why do I want it, and why is it hard to scale? 01 Scaling Git with Bitbucket Data Center 05 What about compliance? 11 Why choose Bitbucket Data Center? 13 01 What is Git, why do I want it, and why is it hard to scale? So. Your software team is expanding and taking on more high-value projects. That’s great news! The bad news, however, is that your centralized version control system isn’t really cutting it anymore. For growing IT organizations, Some of the key benefits Codebase safety moving to a distributed version control system is now of adopting Git are: Git is designed with maintaining the integrity considered an inevitable shift. This paper outlines some of managed source code as a top priority, using secure algorithms to preserve your code, change of the benefits of Git as a distributed version control system history, and traceability against both accidental and how Bitbucket Data Center can help your company scale and malicious change. Distributed development its Git-powered operations smoothly. Community Distributed development gives each developer a working copy of the full repository history, Git has become the expected version control making development faster by speeding up systems in many circles, and is very popular As software development increases in complexity, and the commit process and reducing developers’ among open source projects. This means its easy development teams become more globalized, centralized interdependence, as well as their dependence to take advantage of third party libraries and on a network connection.
    [Show full text]
  • Azure SQL Dev Training Plans
    Complete Practical; Real-time Job Oriented Training Azure SQL Dev Training Plans PLAN A PLAN B PLAN C Course Details Azure SQL Dev SQL Server SQL Dev Azure SQL Dev Azure SQL Dev Azure DevOps Course Curriculum Chapters 21 to 30 Chapters 1 to 30 Chapters 1 to 48 SQL Basics and Query Writing X SQL DB Design, Table Design X Normal Forms, Joins and Queries X Stored Procedures, UDF, Triggers X Advanced Stored Procedures, TVP X CTE, XML, Triggers, PIVOT, Cursors X Dynamic T-SQL Programming X Real-time Project [Banking] X In-depth Query Tuning, Exec” Plans Index Management , Tuning Tools Locks, Deadlocks, Isolation Levels MCSA Certification Exam - 70 761 Azure SQL Database Dev with T-SQL Azure Database Migrations, DTU Elastic Query Processing, Shard Maps MCSA Certification Exam - 70 762 SDLC, Dev & Operations, DevOps X X DevOps Tools, Git & GitHub X X Docker, Kubernetes, AzureDevOps X X Azure Boards, Repos, Tests, Artifacts X X Azure Pipelines (CI, CD), Case Study X X TOTAL DURATION 2 Weeks 6 Weeks 10 Weeks Trainer : Mr. Sai Phanindra T [16+ Yrs of Real-time Exp]. Profile @ linkedin.com/in/saiphanindra www.sqlschool.com For Free Demo: Reach us on +91 9666 44 0801 or +1 956.825.0401 (24x7) Azure SQL Developer Training Module Duration Plan A Plan B Plan C Module 1 SQL Server, T-SQL Programming, Project 4 W X Module 2 Query Tuning, Azure SQL Database Dev 2 W Module 3 Azure DevOps [Service and Server] 4 W X X Total Duration 2 W 6 W 10 W Module 1: SQL, T-SQL, Programming with Stored Procedures Applicable
    [Show full text]