Introduction to Tool Chain Management

a is a collection of tools that work together to automate and streamline software development and operations common benefits include the following integrate tools integrate tools for each phase of the lifecycle plan develop secure test deploy monitor operate automate workflows automate workflows to speed up processes and make them more efficient help identify issues early help teams identify issues early so they can prioritize and address them expediently improve user experience a can help ensure an optimal user experience by identifying issues in real time description for many organizations, the tool chain comprises a significant number of disparate tools in the context of individual applications depending on the devops phase of a given application instance, different tools might be necessary to address the requirements for a specific application in a specific phase for example, azure is often used in the planning phase, but it might not be the only planning tool required by the development team likewise, jenkins and github might be used in the build phase, jenkins for some applications, github for others the decision of which tools to use for which applications at which phase can vary greatly, which means that for some organizations the permutations can be significant management addresses three problem areas understanding the stable of current support tools many of tools sanctioned by teams are open source, which means it's possible that individual teams might take it upon themselves to use github while others build a jira infrastructure workflows and standard practices and operating procedures can devolve and become chaotic in such situations visibility is highly desirable the engineering team is dependent on these tools engineers rely on these tools to set processes and ensure the integrity of those processes so that they understand and can report what is being delivered when and by what means understanding the health and status of these tools is critical to the performance of teams at every phase compliance and security concerns the security and compliance organization (cso) has a vested interest in whether the tools used by the devops teams meet the compliance and security policy and regulations that govern the business cso visibility into tools currently in use is also a significant concern addresses these issues, enabling centralized visibility existing tools are visible for each application at each phase, the status of each tool is available, and compliance and security concerns can be understood and quickly allayed or addressed roles user actions in are role driven actions are granted as privileges associated with roles assigned to individual users the following roles currently exist in the system administrator role create, delete, update, or view defined in the application editor role update and view the and delete the list of tools defined in each phase viewer role view the listed in the service and refresh the tool status for all tools in