Skip to content

Handling Maven GitLab dependencies made easy. Define multiple tokens and selectively apply them to repositories, remove the need for repeating Credential handling blocks for different environments.

License

EPL-2.0, Unknown licenses found

Licenses found

EPL-2.0
LICENSE.md
Unknown
license-header.spotless
Notifications You must be signed in to change notification settings

aepfli/gradle-gitlab-repositories

Gradle GitLab Repositories Plugin

Handling Maven GitLab dependencies easy. Define multiple tokens and selectively apply them to repositories.

Adding a GitLab repository to your project is tiresome, based on the documentation you need to have different Tokens in place for different systems. The GitLab Documentation shows the different types of Tokens, which can be used.

There are:

  • Job-Tokens for CI
  • Private-Tokens for Users
  • Deploy-Tokens for external systems

Additionally, all tokens use a different name for the HttpHeaderCredentials.

Sometimes, there is even the need for gradle-plugin specific repositories and for project specific ones, which can also overlap.

This plugin tries to cover this by allowing to reapply the same plugins, even to each project.

Background

We were in the migration phase from self-hosted development infrastructure (SCM, Nexus, Jenkins, SonarQube) to GitLab and Sonarcloud.io. During the migration phase we needed to support all 3 types of Tokens:

  • Job Token for GitLab CI
  • Deploy Token for 3rd Party systems like Jenkins
  • Private Token for local development

Configuring multiple repositories with repeated configuration was bloating our gradle files. Additionally, minor mistakes like forgetting some parts in the configuration, made it really hard to migrate and follow up.

In the end we investigated and come up with this solution. It will for sure fit not all needs, but it is a starting point. It might help others to easily setup this configuration and if there is demand, there is also room for improvements.

Usage

Configuration

Groovy DSL

gitLab {
	/**
	 * Token configuration also the order in which we try to apply them. 
	 * The key is the name of the token, and the value will be used for application. 
	 * Currently we do have 3 different token classes: 
	 * - PrivateToken 
	 * - DeployToken 
	 * - JobToken (will be always added by default, based on CI_JOB_TOKEN)
	 * */
	token(PrivateToken) {
		it.key = 'private'
		it.value = gitLabPrivateToken // assumed variable in gradle.properties
	}
	token(DeployToken) {
		it.key = 'deploy'
		it.value = System.getenv("GITLAB_DEPLOY_TOKEN")
	}
}

Kotlin DSL

configure<GitlabRepositoriesExtension> {
    /**
     * Token configuration also the order in which we try to apply them.
     * The key is the name of the token, and the value will be used for application.
     * Currently we do have 3 different token classes:
     * - PrivateToken "private"
     * - DeployToken "deploy"
     * - JobToken (will be always added by default, based on CI_JOB_TOKEN)
     * */
    token("private", {
        key = "private"
        value = ""
    })
    token("deploy", {
        key = "tokenAdded"
        value = System.getenv("GITLAB_DEPLOY_TOKEN")
    })
}

Applying the plugin

The plugin can be used within build.gradle and within settings.gradle.

If there is no need to apply special repositories to the build.gradle it might be enough, to just apply it to the settings.

Groovy DSL

build.gradle

plugins {
	id 'at.schrottner.gitlab-repositories' version '<version>'
}

settings.gradle

buildscript {
	// ...
	dependencies {
		classpath 'at.schrottner.gradle.gitlab-plugin:gitlab-repositories:<version>'
	}
}

apply plugin: 'at.schrottner.gitlab-repositories'

Kotlin DSL

build.gradle.kts

plugins {
    id("at.schrottner.gitlab-repositories") version "<version>"
}

settings.gradle.kts

buildscript {
    // ..
    dependencies {
        classpath("at.schrottner.gradle.gitlab-plugin:gitlab-repositories:<version>")
    }
}

apply(plugin = "at.schrottner.gitlab-repositories")

Repository handling

Adding repositories for dependencies

The plugin offers you a nice helper method inspired by gradle-jruby-plugin to easily add repositories.

Groovy DSL

repositories {
	maven gitLab.project(projectId)
	maven gitLab.project(projectId) {
		name = "custom name"
		tokenSelektor = "" // a name of a configured token
		tokenSelectors = [] // a list of configured tokens, which will be checked based on their order in this set
	}
	maven gitLab.group(groupId)
	maven gitLab.group(groupId) {
		name = "custom name"
		tokenSelektor = "" // a name of a configured token
		tokenSelectors = [] // a list of configured tokens, which will be checked based on their order in this set
	}
}

Kotlin DSL

repositories {
    val gitLab = the<GitlabRepositoriesExtension>()
    maven(gitLab.project(projectId))
    maven(gitLab.project(projectId) {
        name.set("custom name")
        tokenSelektor.set("") // a name of a configured token
        tokenSelectors.addAll(/*...*/) // a list of configured tokens, which will be checked based on their order in this set
    })
    maven(gitLab.group(groupId))
    maven(gitLab.group(groupId) {
        name.set("custom name")
        tokenSelektor.set("") // a name of a configured token
        tokenSelectors.addAll(/*...*/) // a list of configured tokens, which will be checked based on their order in this set
    })
}

Adding repositories for publishing

Be aware that this has to be a projectId - you are not able to upload to groups!

Groovy DSL

For adding a repository to the maven-publish repositories please use following method.

publishing {
    repositories {
        maven gitLab.upload(projectId)
        maven gitLab.upload(projectId) {
            name = "custom name"
            tokenSelektor = "" // a name of a configured token
            tokenSelectors = [] // a list of configured tokens, which will be checked based on their order in this set
        }
    }
}

Kotlin DSL

publishing {
    repositories {
        val gitLab = the<GitlabRepositoriesExtension>()
        maven(gitLab.upload(projectId) {
            name.set("GitLab")
            tokenSelector.set("testToken")
        })
    }
}

Adding a repository with defaults

This will add a repository and will apply conditions for the first token matching, and not being empty.

// pluginManagment.repositories { // when in settings.gradle
repositories {
	maven gitLab.project(1)
	maven gitLab.group(1)
}

Adding a repository with specific tokens

We can define which tokens should be taken into account (currently order of parameter is ignored)

gitLab.project(1) {
	tokenSelectors = ['private', 'deploy']
}
gitLab.group(1) {
	tokenSelectors = ['private', 'deploy']
}

Additionally, we can provide one specific token to be used, if the token is not set, or empty, nothing will be done.

gitLab.project(1) { tokenSelector = 'deploy' }
gitLab.group(1) { tokenSelector = 'deploy' }

Comparison

with the plugin

plugins {
	id 'maven'
	id 'maven-publish'
	id 'at.schrotter.gitlab-repositories' version '<version>'
}

gitLab {
	// jobToken will be applied automatically
	token(DeployToken) {
		name = "deployToken"
		value = System.getenv("GITLAB_DEPLOY_TOKEN")
	}
	token(PrivateToken) {
		name = "privateToken"
		value = gitLabPrivateToken
	}
}

repositories {
	maven gitLab.group("ID")
}

publishing {
	repositories {
		maven gitLab.upload("ID")
	}
}

without this plugin

plugins {
	id 'maven'
	id 'maven-publish'
}

repositories {
	maven {
		url 'GitLab Url with ID'
		name "GitLab"
		if (System.getenv("CI_JOB_TOKEN")) {
			credentials(HttpHeaderCredentials) {
				name = 'Job-Token'
				value = System.getenv("CI_JOB_TOKEN")
			}
		} else if (System.getenv("GITLAB_DEPLOY_TOKEN")) {
			credentials(HttpHeaderCredentials) {
				name = 'Deploy-Token'
				value = System.getenv("GITLAB_DEPLOY_TOKEN")
			}
		} else {
			credentials(HttpHeaderCredentials) {
				name = 'Private-Token'
				value = gitLabPrivateToken
			}
		}
		authentication {
			header(HttpHeaderAuthentication)
		}
	}
}

publishing {
	repositories {
		maven {
			url 'GitLab Url with ID'
			name "GitLab"
			if (System.getenv("CI_JOB_TOKEN")) {
				credentials(HttpHeaderCredentials) {
					name = 'Job-Token'
					value = System.getenv("CI_JOB_TOKEN")
				}
			} else if (System.getenv("GITLAB_DEPLOY_TOKEN")) {
				credentials(HttpHeaderCredentials) {
					name = 'Deploy-Token'
					value = System.getenv("GITLAB_DEPLOY_TOKEN")
				}
			} else {
				credentials(HttpHeaderCredentials) {
					name = 'Private-Token'
					value = gitLabPrivateToken
				}
			}
			authentication {
				header(HttpHeaderAuthentication)
			}
		}
	}
}

About

Handling Maven GitLab dependencies made easy. Define multiple tokens and selectively apply them to repositories, remove the need for repeating Credential handling blocks for different environments.

Topics

Resources

License

EPL-2.0, Unknown licenses found

Licenses found

EPL-2.0
LICENSE.md
Unknown
license-header.spotless

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •