DevOps Tools/Integration/Jenkins Gitlab
From r00tedvw.com wiki
(Difference between revisions)
| Line 2: | Line 2: | ||
=[[DevOps_Tools/Integration/Jenkins_Gitlab|Jenkins with Gitlab]]= | =[[DevOps_Tools/Integration/Jenkins_Gitlab|Jenkins with Gitlab]]= | ||
Make sure that you have [[DevOps_Tools/CI/Jenkins#Jenkins|Jenkins]] and [[DevOps_Tools/SCM/GitLab#Git_Lab|Gitlab]] installed. | Make sure that you have [[DevOps_Tools/CI/Jenkins#Jenkins|Jenkins]] and [[DevOps_Tools/SCM/GitLab#Git_Lab|Gitlab]] installed. | ||
| + | |||
| + | ==Configure Gitlab== | ||
| + | You will need to have at least (1) project setup, though there doesn't need to be anything in it. | ||
| + | *Log-in to the Gitlab web portal > [click] Projects > [click] New project > give it: | ||
| + | :*Project Name | ||
| + | :*Description | ||
| + | :*Visibility level (i've chosen private) | ||
| + | <br> | ||
| + | Next you'll need to add a deploy key, which is found by: | ||
| + | *[click] on the project name > go to Settings > [click] Repository > [click] Expand next to Deploy Keys > and define the following: | ||
| + | :*Title - pick a easy description that will help identify it as the public ssh key from your jenkins server | ||
| + | :*Key - Paste the public ssh key from your jenkins server. | ||
| + | :*Write access allowed - make sure to check the box to allow. | ||
==Configure Jenkins== | ==Configure Jenkins== | ||
First thing we need to do is give Jenkins a copy of the Private SSH key that was created for the jenkins user on the jenkins server.<br> | First thing we need to do is give Jenkins a copy of the Private SSH key that was created for the jenkins user on the jenkins server.<br> | ||
*Log-in to the Jenkins web portal > [click] credentials > [click] system > [click] Global credentials > [click] Add credentials | *Log-in to the Jenkins web portal > [click] credentials > [click] system > [click] Global credentials > [click] Add credentials | ||
Obviously you can create a domain for a greater level of security instead of using the unrestricted global credentials group | Obviously you can create a domain for a greater level of security instead of using the unrestricted global credentials group | ||
Revision as of 15:47, 4 January 2019
Overview | Continuous Integration (CI) | Source Control Management (SCM) | Containerization | Configuration | Integration
Jenkins with Gitlab
Make sure that you have Jenkins and Gitlab installed.
Configure Gitlab
You will need to have at least (1) project setup, though there doesn't need to be anything in it.
- Log-in to the Gitlab web portal > [click] Projects > [click] New project > give it:
- Project Name
- Description
- Visibility level (i've chosen private)
Next you'll need to add a deploy key, which is found by:
- [click] on the project name > go to Settings > [click] Repository > [click] Expand next to Deploy Keys > and define the following:
- Title - pick a easy description that will help identify it as the public ssh key from your jenkins server
- Key - Paste the public ssh key from your jenkins server.
- Write access allowed - make sure to check the box to allow.
Configure Jenkins
First thing we need to do is give Jenkins a copy of the Private SSH key that was created for the jenkins user on the jenkins server.
- Log-in to the Jenkins web portal > [click] credentials > [click] system > [click] Global credentials > [click] Add credentials
Obviously you can create a domain for a greater level of security instead of using the unrestricted global credentials group
