| ... | @@ -25,7 +25,8 @@ Creating a Jenkins job for your Gitlab project can be broken into 3 major steps: | 
... | @@ -25,7 +25,8 @@ Creating a Jenkins job for your Gitlab project can be broken into 3 major steps: | 
| 
 | 
     3. **Credentials**: `jenkins`
 | 
 | 
     3. **Credentials**: `jenkins`
 | 
| 
 | 
     4. **Repository browser**: `gitlab`
 | 
 | 
     4. **Repository browser**: `gitlab`
 | 
| 
 | 
     5. Then enter your Gitlab URL - e.g. `https://vc.digitec.local/kd/kd-ui/`
 | 
 | 
     5. Then enter your Gitlab URL - e.g. `https://vc.digitec.local/kd/kd-ui/`
 | 
| 
 | 
     6. Grab the Gitlab version from [Gitlab Admin Area](https://vc.digitec.local/admin) and enter it in the **Version** text input - e.g. `6.6.5`
 | 
 | 
     6. Grab the Gitlab version from [Gitlab Admin Area](https://vc.digitec.local/admin) and enter the major.minor version in the **Version** text input - e.g. `6.6`
 | 
 | 
 | 
 | 
        * **IMPORTANT** - At the time of this writing, if you place a `patch` number in your version, Jenkins will throw an error.  So, if the Gitlab version is `6.6.5`, you should enter `6.6` into the Jenkins text input.
 | 
| 
 | 
 7. Under **Build Triggers**, enable **Poll SCM**
 | 
 | 
 7. Under **Build Triggers**, enable **Poll SCM**
 | 
| 
 | 
 8. Configure the **Build** section. This varies per project. The following is the build for the `kd-ui` project
 | 
 | 
 8. Configure the **Build** section. This varies per project. The following is the build for the `kd-ui` project
 | 
| 
 | 
     1. From **Add Build Step** dropdown, choose **Execute Shell**
 | 
 | 
     1. From **Add Build Step** dropdown, choose **Execute Shell**
 | 
| ... |  | ... |  |