Skip to content
This repository has been archived by the owner. It is now read-only.
Browse files

first draft for root documentation is done

  • Loading branch information...
baymac committed Jun 9, 2019
1 parent ddb7d35 commit afe6390b06c0c3a29edcaeddd805c48951349215
@@ -5,8 +5,6 @@
* GitLab Server Plugin
* GitLab Branch Source Plugin

**This plugin is being developed as a part of GSoC 2019 project [Multi branch Pipeline Support for GitLab](**

To fully be able to run a Jenkins Continuous Integration on a GitLab repository or project, you require three plugins:

1. [GitLab API Plugin]( - Wraps GitHub Java API
@@ -234,13 +232,102 @@ Assuming plugin installation has been done already.

6. Adding a Personal Access Token Credentials:

This is a manual setup. To automatically generate Personal Accees Token see next section.

i. User is required to add a `GitLab Personal Access Token` type credentials entry to securely persist the token inside Jenkins.

ii. Generate a Personal Access Token on your GitLab Server

a. Select profile dropdown menu from top-right corner

b. Select `Settings`

c. Select `Access Token` from left column

d. Enter a name | Set Scope to `api`,`read_user`, `read_repository`

e. Select `Create Personal Access Token`

f. Copy the token generated

iii. Return to Jenkins | Select `Add` in Credentials field | Select `Jenkins`

iv. Set `Kind` to GitLab Personal Access Token

v. Enter `Token`

vi. Enter a unique id in `ID`

vii. Enter a human readable description


viii. Select `Add`

7. Testing connection:

i. Select your desired token in the `Credentials` dropdown

ii. Select `Test Connection`

iii. It should return something like `Credentials verified for user {username}`

8. Select `Apply` (at the bottom)

9. GitLab Server is now setup on Jenkins

#### Creating Personal Access Token within Jenkins

User does not have to go to your GitLab Server settings for creating GitLab Personal Access Token, this can be done
automatically inside Jenkins itself.

1. Select `Advanced` at the bottom of `GitLab` Section.

2. Select `Manage Additional GitLab Actions`

3. Select `Convert login and password to token`

4. Set the `GitLab Server URL`

5. There are 2 options to generate token;

i. `From credentials` - To select an already persisting Username Password Credentials or add an Username Password
credential to persist it.

ii. `From login and password` - If this is a one time thing then you can directly enter you credentials to the text boxes
and the username/password credential is not persisted.

6. After setting your username/password credential, select `Create token credentials`.

7. The plugin will automatically create a Personal Token Access Token in your GitLab Server for the give user and with the
required scope. You can go back to the GitLab Server Configuration to select the new credentials generated. Identify the new
credentials with the `id` returned by token creator. It should be a a 128-bit long UUID-4 string (36 characters).


### Setting up GitLab for jobs

This section is a **Work in Progress**. Will be updated upon release.

## Issues

This project uses Jenkins [JIRA]( to track issues. You can file issues under `gitlab-branch-source-plugin` component.

## Acknowledgements

This plugin is built and maintained by the Google Summer of Code (GSoC) Team for
[Multi branch Pipeline Support for GitLab](

The team consists of:

* [baymac]( (Student)
* [LinuxSuRen]( (Mentor)
* [Marky]( (Mentor)
* [Joseph]( (Mentor)
* [Justin]( (Mentor)
* [Jeff]( (Mentor)

Honorable Mentions:
6. [Oleg]( (The org admin who helps with all technical issues)
7. [Greg]( (The creator of GitLab4J APIs)
8. [Stephen]( (The creator of SCM related Plugins)
Binary file not shown.
BIN -130 Bytes (100%) docs/img/gitlab-server.png
Binary file not shown.
Binary file not shown.

0 comments on commit afe6390

Please sign in to comment.
You can’t perform that action at this time.