jenkins-gitlab-merge-request-builder-plugin | allows jenkins to build merge requests | Plugin library

by timols Java Version: 2.0.1 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | jenkins-gitlab-merge-request-builder-plugin Summary

jenkins-gitlab-merge-request-builder-plugin is a Java library typically used in Plugin, Ruby On Rails, Gradle applications. jenkins-gitlab-merge-request-builder-plugin has no bugs, it has no vulnerabilities, it has build file available and it has low support. However jenkins-gitlab-merge-request-builder-plugin has a Non-SPDX License. You can download it from GitHub.

A plugin that allows jenkins to build merge requests in Gitlab

Support

Quality

Security

License

Reuse

Support

jenkins-gitlab-merge-request-builder-plugin has a low active ecosystem.

It has 345 star(s) with 129 fork(s). There are 24 watchers for this library.

It had no major release in the last 6 months.

There are 65 open issues and 86 have been closed. On average issues are closed in 89 days. There are 5 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of jenkins-gitlab-merge-request-builder-plugin is 2.0.1

Quality

jenkins-gitlab-merge-request-builder-plugin has 0 bugs and 0 code smells.

Security

jenkins-gitlab-merge-request-builder-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jenkins-gitlab-merge-request-builder-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

jenkins-gitlab-merge-request-builder-plugin has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

jenkins-gitlab-merge-request-builder-plugin releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Installation instructions are available. Examples and code snippets are not available.

jenkins-gitlab-merge-request-builder-plugin saves you 840 person hours of effort in developing the same functionality from scratch.

It has 1925 lines of code, 170 functions and 28 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed jenkins-gitlab-merge-request-builder-plugin and discovered the below as its top functions. This is intended to give you an instant insight into jenkins-gitlab-merge-request-builder-plugin implemented functionality, and help decide if they suit your requirements.

Start the build
Find trigger
Build a Gitlab merge request
Connect to GitLab
Add environment variables to the Gitlab environment
Called when a queue is pressed
Initialize the trigger
Stops the job
Checks for GitHub webhooks

Get all kandi verified functions for this library.

jenkins-gitlab-merge-request-builder-plugin Key Features

No Key Features are available at this moment for jenkins-gitlab-merge-request-builder-plugin.

jenkins-gitlab-merge-request-builder-plugin Examples and Code Snippets

No Code Snippets are available at this moment for jenkins-gitlab-merge-request-builder-plugin.

Community Discussions

Trending Discussions on jenkins-gitlab-merge-request-builder-plugin

GitLab: Editing the merge request description triggers a merge request hook being sent

QUESTION

GitLab: Editing the merge request description triggers a merge request hook being sent

Asked 2019-Dec-18 at 14:12

For my repository on GitLab I have a Merge Request Hook configured which triggers a build on a Jenkins CI machine. The hooks works as expected when a merge request is opened.

The webhook is configured with the following triggers:

URL: https://example.com/project/ExampleApp_merge_requests
Push events: Enabled
Merge request events: Enabled
Enable SSL verification: Off

Lately, when I edit the description of the merge requests then the hook also notifies the CI machine.
Here is an example POST request:

Request headers: ...

ANSWER

Answered 2019-Apr-02 at 12:25

Under triggers (Settings -> integrations) perform the below:

Enable push events (optional branch name - Branch is created via push events even before MR is possible)
Enable MR event triggers in your project repo

This URL will be triggered when a merge request is created/updated/merged

In Jenkins Plugin configuration -

Check "Push Events" (Any commits by way of direct Push or Creation)
Un-check "Opened Merge Request Events"
Check "Accepted Merge Request Events" (Any commits by way of Merge Request)

Source https://stackoverflow.com/questions/55284986

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install jenkins-gitlab-merge-request-builder-plugin

Ensure that a Jenkins user exists within GitLab and has access to the repository. For GitLab version < 8.4.X: ensure that the user has Reporter level access to the project. For GitLab version >= 8.4.X: ensure that the user has Developer level access to the project. Please note that if you would like to use the Auto-merge feature Jenkins needs to have Developer access to the project.
Install the plugin in Jenkins. The plugin is hosted on the Jenkins Plugin repository Go to Jenkins -> Manage Plugins -> Available Search for GitLab Merge Request Builder And install it Ensure you restart Jenkins
Go to Manage Jenkins -> Configure System -> GitLab Merge Request Builder
Set the GitLab Host URL to the base URL of your GitLab server
Set your Jenkins Username for the Jenkins user (defaults to jenkins)
Set your Jenkins API Token for the Jenkins user. This can be found by logging into GitLab as Jenkins and going to the user profile section.
Set/change any of the other available parameters as necessary. If you host GitLab over an SSL connection you may want to enable ignoring certificate errors.
Save to preserve your changes.
Go to Manage Jenkins -> Configure Global Security and set Markup Formatter to Safe HTML. It will make Jenkins display links in build history properly.

Support

GitLab version < 8.1: use v1.2.4 of this pluginGitLab version >= 8.1 < 11: use v2.0.1 of this pluginGitLab version >= 11: use the latest version of this plugin

Find more information at: