GitLab: Plan phase

gitlab is a single application that spans the entire software development lifecycle this makes gitlab unique and creates a streamlined software workflow, unlocking your organization from the constraints of a pieced together toolchain supports your use of gitlab and gitlab enterprise for to pull data from gitlab, you must configure a gitlab account gitlab application requires the following information for gitlab name local account name it could be any string and is used only for reference user username for git generally, the email id with which the user logged in to git token personal access token tokens can be generated from the following menu selection settings → access tokens the personal access token requires permissions within the following recommended scopes application also requires the following gitlab credentials gitendpoint gitlab name neha gitlab user a user\@domain com token personal access token gitlab enterprise application requires the following information for gitlab enterprise name local account name it could be any string and is used only for reference host git api url of the git host eg, api url will be like https //gitlab gravitant net user username for git generally the email id with which user logged in to git token personal access token the personal access token requires the permissions within the following recommended scopes application also requires the following gitlab enterprise credentials gitendpoint gitlab enterprise host https //gitlab gravitant net name rajat user a user\@domain com token personal access token configuring for gitlab plan phase and recent customers the procedures in this section are valid only for customers onboarded 6 june 2024 or after procedures for legacy customers are provided in the subsequent section configuring for gitlab, legacy customers use the following procedure to configure the for azure pipelines tools must be configured for a specific application in a specific devops phase in step 2 of the following procedure, you are choosing the application and devops phase to associate with gitlab as part of the configuration procedure click settings & utilities → application configuration you will see a list of existing applications select the existing application for which you want to configure gitlab or create a new application click the overflow menu (vertical ellipsis) on the plan row for the selected application select add new tool configuration from the overflow menu the service displays the add tool configuration form select gitlab for tool engine click submit onboarding gitlab plan phase after configuring gitlab, you must onboard the technical service use the following procedure click the overflow menu for the selected application select onboard technical service the service displays the onboard technical service form select plan for devops phase the service displays the tool engine field select gitlab for tool engine the service displays the select connection field select the appropriate connection the service displays the select organization field select the appropriate organization the service displays the select projects field select the appropriate project the service displays the repository name field select the appropriate repository click onboard the service navigates to the application configuration page you now have the option of clicking the overflow menu for develop and selecting edit/delete tools configuration to confirm that gitlab has been fully configured deleting gitlab as a technical service the administrator may, at will, delete the gitlab technical service use the following procedure navigate to → settings & utilities → application configuration expand the application to view all associated phases click the overflow menu for plan click delete technical service click gitlab for select tools configured the service displays the select organization field select the appropriate organization the service displays the select projects field select the appropriate project click delete configuring for gitlab, legacy customers the procedures in this section are valid only for customers onboarded before 6 june 2024 if the user wants to track all the repository comprising this organization (organization level), then he would need to select orgs and, if the user wants to track a particular repository (repository level), he would need to select repos organization level tracking for this type of tracking, some selections have to be made in the system, as described in the following list account refers to the account through which the tracking is to be done select tracking type users must select organization for org level tracking search organization by selecting here, a list of all organizations for the selected account but not tracked by application select any organization you want to track and select configure repository level tracking for this type of tracking, some selections have to be made in the system, as described in the following list account refers to the account through which the tracking is to be done select tracking type user must select repository for repo level tracking search organization by selecting here, a list of all organizations for the selected account but not tracked by application select any organization to be tracked and select configure select any organization you want to track and select configure search repository by selecting here, a list will be displayed with all the repositories that are part of the selected organization but not tracked select any repository you want to track and select configure the sync feature scans current data for visibility after configuring credentials periodically the intervals are set as follows the account sync interval is set to 5 mins refresh current data the account delete interval is set to 7 mins all deleted accounts updated the history pulled interval is set to 180 days data history configuring gitlab to complete the integration of gitlab, you must complete a configuration process kyndryl supports two different configuration processes only one of which your organization has subscribed if your organization was onboarded before 6 june, 2024, you are subject to the legacy process (legacy customers) if your organization was onboarded on 6 june 2024 or after, you are subject to the new process (recent customers) refer to the appropriate document in the following list application configuration legacy customers docid\ m1tce9nzb0dguu9w8zogw creating an application docid\ r oxvj9o68noa0fc6j5ks the configuration mechanisms that require these processes are in a transition phase driven by the fact that each tool must be individually adapted for the new mechanism, which is more efficent than the legacy mechanism both processes are supported until the transition of all supported tools from the old mechanism to the new mechanism is complete