Migrating to Git as your distributed version control system will improve the overall efficiency of your development teams, but initially, developers will face a steep learning curve.A funny thing happened on the way to Kansas. Failure to address this challenge often results in increased time to ship your code and decreased code stability. GitKraken creates a seamless process for onboarding to Git and helps streamline and standardize workflow processes. GitKraken’s Gitlab integration also offers the ability to accomplish the following actions.Ĭlick on the links below to navigate to the related sections on this page: Many of the features offered by the GitKraken Git GUI, like issue tracking integrations and intuitive merge conflict resolution, take team collaboration to the next level. Add remotes for GitLab.SonarQube's integration with GitLab Self-Managed and allows you to maintain code quality and security in your GitLab projects.With this integration, you'll be able to: Authenticate with GitLab - Sign in to SonarQube with your GitLab credentials.Import your GitLab projects - Import your GitLab Projects into SonarQube to easily set up SonarQube projects.Analyze projects with GitLab CI/CD - Integrate analysis into your build pipeline. ![]() Starting in Developer Edition, SonarScanners running in GitLab CI/CD jobs can automatically detect branches or merge requests being built so you don't need to specifically pass them as parameters to the scanner. Report your Quality Gate status to your merge requests - (starting in Developer Edition) See your Quality Gate and code metric results right in GitLab so you know if it's safe to merge your changes. ![]() Integration with GitLab Self-Managed requires at least GitLab Self-Managed version 11.7. Starting in Developer Edition, you can analyze multiple branches and merge requests.īranch AnalysisĬommunity Edition doesn't support the analysis of multiple branches, so you can only analyze your main branch. ![]() You can delegate authentication to GitLab using a dedicated GitLab OAuth application. Scopes – select api if you plan to enable group synchronization.Redirect URI – enter your SonarQube URL with the path /oauth2/callback/gitlab.Name – your app's name, such as SonarQube.Specify the following settings in your OAuth app: You can find general instructions for creating a GitLab OAuth app here. Select read_user if you only plan to delegate authentication.Īfter saving your application, GitLab takes you to the app's page. Here you find your Application ID and Secret. Secret – the Secret is found on your GitLab app's page.Application ID – the Application ID is found on your GitLab app's page.Set the following settings to finish setting up GitLab authentication: Keep these handy, open your SonarQube instance, and navigate to Administration > Configuration > General Settings > DevOps Platform Integrations > GitLab > Authentication. On the login form, the new "Log in with GitLab" button allows users to connect with their GitLab accounts. ![]() GitLab group synchronizationĮnable Synchronize user groups at Administration > Configuration > General Settings > DevOps Platform Integrations > GitLab to associate GitLab groups with existing SonarQube groups of the same name. To synchronize a GitLab group or subgroup with a SonarQube group, name the SonarQube group with the full path of the GitLab group or subgroup URL.įor example, with the following GitLab group setup: GitLab users inherit membership to subgroups from parent groups. Importing your GitLab projects into SonarQube You should name your SonarQube group my-group to synchronize it with your GitLab group and my-group/my-subgroup to synchronize it with your GitLab subgroup. Setting up the import of GitLab projects into SonarQube allows you to easily create SonarQube projects from your GitLab projects.
0 Comments
Leave a Reply. |