Mapping technical services

acquire an understanding of technical service mapping to optimize operational effectiveness throughout the devops lifecycle technical services are auto discovered for a few endpoints but mapping your technical services is always a good idea, for example, if you see multiple entries for a single service for the different endpoints in the configure technical services table, you can map them together to a single service as your pipeline as an example, keep in mind that if a repo in git is named demo121 and in travis (build) it is demo121, but in sonarqube (test) the name of the project linked to the build tool is releasedemo, the releasedemo of sonarqube (test) can be mapped/ linked to the above technical service (demo121) resulting in creating a single service for your pipeline note this stage is important as it has a direct impact on metering the following is an example list of the different technical services identified by after configuring tools & credentials also, this table shows all the technical services identified by by default and in this example, the git , test and build tools were configured earlier so respective technical services are mentioned later technical services testproject (test) backend (test) mcmp java pipeline (test) demo for aparna (test) mcmp java pipeline (team mcmp java), (develop git) mcmp devops project (build) mcmp testgoproject (build) mcmp task gophercise (develop git), (build), (test), (application project!) recover (team mgmtuser), (develop git), (build), (test) mcmp simplemavenproject (build) mcmp testmavenproject (build) in order to link technical services, you must complete the following steps go to settings & utilities and then click on configure technical services in the associate technical service tab, click on the overflow menu, and choose link technical services tile in the technical services table select any service that has to be mapped across the pipeline mcmp java pipeline is a service identified by git and test we can map them together and make it a single service as our pipeline then, click on the git mcmp java pipeline as we want to link our test service to our git service select the test service and click update technical service now, if we search for mcmp java pipeline we see that both test and git service have been linked together as per the pipeline requirements note important linking technical services of the same type is not possible, for example, a service registered by sonargube and byot is not possible as both have the same service type if a service is registered by jira and git are linked, two separate rows will be shown in the develop dashboard technical services view, with the same name but will show individual tools data