AzureDevOps

Editor's Notes

• #5: Full traceability OOTB, SaaS solution, always upto date, no maintenance of our own build machine, hosted in various region ADO is not TFS in Cloud Cross platform dev, not for .NET, not for Windows TFS-2005 to 2018 ADO Server – 2019,2020 VSO-2013 VSTS-2015 ADO-2018 ADO/ADO Server - 2020 (its same)
• #7: https://docs.microsoft.com/en-us/azure/devops/organizations/security/access-levels?view=azure-devops https://dev.azure.com/ https://signup.live.com/ Account Types: MSA, AAD , AAD Guest
• #9: Process, workitems, traceablility, planning, sprint, backlog, dashboard (Kanban, agile) https://docs.microsoft.com/en-us/azure/devops/boards/work-items/guidance/choose-process
• #10: Process, workitems, traceablility, planning, sprint, backlog, dashboard (Kanban, agile) https://docs.microsoft.com/en-us/azure/devops/boards/work-items/guidance/choose-process
• #12: Code Review=Pull Requests
• #14: https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema/?view=azure-pipelines A linear sequence of operations that make up a job YAML- Yet Another Markup Language Cloud and Self Hosted Agents TFVC=Classic JSON based pipeline GIT= Yaml based pipeline CI=Triggers builds/integrations CD=Delivers to targeted environment Build automation, CI, deployment automation CD, traceability and compliances, hooks for other products
• #16: Planned and exploratory testing solution, capture rich data, tests across web and desktop, get end to end traceability For Web- need to add the extension Tests & Feedback and configure with your repository
• #18: To protection against outages of public feeds and corruptions of packages. Also, to enable insights into packages that are used by your team. And you can use it for your private packages store and distribution in your organization. nuget.exe push -Source "headless" -ApiKey headless ".nupkg path" nuget.exe install <PackageName> -Source "headless“ CreadentialProvider.Microsoft -U https://pkgs.dev.azure.com/awemind/_packaging/awemind/nuget/v3/index.json Package management , nuget, npm; artifact repo, track usage of external packages, traceability [Information] [CredentialProvider]Username: VssSessionToken [Information] [CredentialProvider]Password: 4xca2vprvize6augxuypo7pjy5mcdxuo5dbav7lwzonr2vc2nwwa <?xml version="1.0" encoding="utf-8"?> <configuration> <packageSources> <clear /> <add key="awemind" value="https://pkgs.dev.azure.com/awemind/_packaging/awemind/nuget/v3/index.json" /> </packageSources> </configuration> Restore Package: nuget.exe restore Publish Package: nuget.exe push -Source "awemind" -ApiKey az <packagePath>
• #20: Dev Centric = Setup code scanning for your repository such as SAST (Static Application Security Testing) https://github.com/github/codeql/discussions/7671 https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository Git: ML based alerts vs Standard Alert
• #21: https://akshayranganath.github.io/Git-Pull-Handling-Merge-Conflict/