The gitlab-release-maven-plugin creates tags on your GitLab Repository by your project version in your maven build.
<plugin>
<groupId>com.avides.gitlab</groupId>
<artifactId>gitlab-release-maven-plugin</artifactId>
<version>2.2.0-RELEASE</version>
</plugin>
<plugin>
<groupId>com.avides.gitlab</groupId>
<artifactId>gitlab-release-maven-plugin</artifactId>
<version>2.2.0-RELEASE</version>
<configuration>
<gitlabHost>http://your-custom-gitlab-domain/</gitlabHost>
<gitlabAccessToken>GITLAB_ACCESS_TOKEN</gitlabAccessToken>
<gitlabRepositoryNamespace>repository-namespace</gitlabRepositoryNamespace>
<gitlabRepositoryName>project-name</gitlabRepositoryName>
<projectVersion>0.1.0-RELEASE</projectVersion>
<gitlabPreReleaseDesired>true</gitlabPreReleaseDesired>
<gitlabBranchName>YOUR_DEPLOYMENT_BRANCH</gitlabBranchName>
</configuration>
</plugin>
Property | Description | Required |
---|---|---|
gitlabHost | Your custom GitLab URL (default: https://gitlab.com ) |
No |
gitlabAccessToken | Your User GitLab Access Token (Pass this token directly in the execute command, -DgitlabAccessToken=ACCESS_TOKEN ) |
Yes |
gitlabRepositoryNamespace | Repository namespace (If project.scm.url is set in your pom, it will be resolved automatically.) |
No |
gitlabRepositoryName | Repository name (default: ${project.name} ) |
No |
projectVersion | Project version and finally the Release-Tag name (default: ${project.version} ) |
No |
gitlabPreReleaseDesired | If true , PRE-Releases will be create a Release-Tag, otherwise not (default: false ) |
No |
gitlabBranchName | Your deployment branch (default: master ) |
No |
mvn gitlab-release:release -DgitlabAccessToken=ACCESS_TOKEN