gitlab-branch-source-plugin | Jenkins-Plugin to create | Continuous Deployment library

by Argelbargel Java Version: 0.7.9-dev License: GPL-2.0

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

kandi X-RAY | gitlab-branch-source-plugin Summary

gitlab-branch-source-plugin is a Java library typically used in Devops, Continuous Deployment, Jenkin, Docker applications. gitlab-branch-source-plugin has no bugs, it has no vulnerabilities, it has build file available, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

The GitLab Branch Source Plugin allows you to create a new project based on the repository structure based on your GitLab projects. It is heavily inspired by the GitHub Branch Source Plugin, builds upon the GitLab Plugin and uses the Gitlab Java API Wrapper for communication with GitLab. The GitLab Branch Source Plugin scans your GitLab server for projects according to criteria you can specify. The only restriction is that your projects must contain a Jenkinsfile with the definition of the pipeline used to build the project. You can have different Pipeline scripts defined in project branches, or add and remove Jenkinsfiles depending on your use cases. After a project is imported, Jenkins immediately runs a job. Removing a Pipeline script from a branch or from the entire project, removes the item from the view. You can restrict imports on the GitLab Branch Source configuration page. Restrictions include regular expressions for origin branches, merge requests from the original projects or it's forks etc. Like the GitHub Branch Source Plugin this plugin creates each repository as a folder containing each branch with a Jenkinsfile in the top level directory as a different job. When the proper webhooks are configured, the GitLab Branch Source Plugins automatically detects new projects, branches and merge requests, adds new jobs accordingly and builds them. If Jenkins (or rather the user configured to communicate with GitLab) is allowed to do so, it will setup these webhooks automatically for you. When Jenkins is allowed to do so build results will be reported back to GitLab. You can choose whether only the build result (success/failure) get reported or if Jenkins reports every stage defined in your pipeline.

Support

Quality

Security

License

Reuse

Support

gitlab-branch-source-plugin has a low active ecosystem.

It has 76 star(s) with 46 fork(s). There are 13 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 85 have been closed. On average issues are closed in 581 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gitlab-branch-source-plugin is 0.7.9-dev

Quality

gitlab-branch-source-plugin has 0 bugs and 0 code smells.

Security

gitlab-branch-source-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

gitlab-branch-source-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gitlab-branch-source-plugin is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

gitlab-branch-source-plugin releases are available to install and integrate.

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

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

gitlab-branch-source-plugin saves you 2376 person hours of effort in developing the same functionality from scratch.

It has 5182 lines of code, 598 functions and 102 files.

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

Top functions reviewed by kandi - BETA

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

Handles the listener
Handles the hooks
Creates a new SCMS source event
Creates a new commit request event
Called when a build is started
Publishes the build status of a build
Attaches a graph listener to the graph
Build a SCM with the specified revision
Connect to the GitLab API
Called when a build completes
Accepts a merge request
Gets a list of remote remotes for the given SCM source
Compares the webHook for equality
Compares two objects for equality
Checks if this link action is equal to
Compares objects for equality
Compares GitLabAvatar metadata for this project
Get the merge request head
Replies if the given category is enabled
Returns a list of RefSpec objects for this source
Compares GitHeadMetadata action for equality
Gets the branch specs
Returns a list of connection requirements for gitlab - connection
Compares this object to another
Initialize icons
Checks to see if the path is configured

Get all kandi verified functions for this library.

gitlab-branch-source-plugin Key Features

No Key Features are available at this moment for gitlab-branch-source-plugin.

gitlab-branch-source-plugin Examples and Code Snippets

No Code Snippets are available at this moment for gitlab-branch-source-plugin.

Community Discussions

Trending Discussions on gitlab-branch-source-plugin

Jenkins: Access job/plugin configuration values inside pipeline

QUESTION

Jenkins: Access job/plugin configuration values inside pipeline

Asked 2021-Jan-25 at 19:37

I am trying the access the values set on a job's configuration page from within my pipeline. These values are not made available as params, nor are they injected as envvars.

Setup

Jenkins, v2.263.1
GitLab Branch Source plugin, v1.5.3 (link)
Multibranch pipeline job which is pointed to a Gitlab repo
Remote Jenkinsfile Provider, v1.13 (link)

Problem

Ordinarily, one would have a Jenkinsfile in the root of the repo and therefore the scm would be associated with the repo we want to checkout and build. However, in my case the code I want to build is in a different repo to the Jenkinsfile (hence the Remote Jenkinsfile Provider plugin).

This means that I need to checkout the code I wish to build as an explicit step in the pipeline, and to do that I need to know the repo. This repo is, however, already defined in the job config.

The Branch Source plugin does export things like the branch name or merge request number/branch/target into appropriate envvars, but NOT the actual repo.

As this is a multibranch pipeline, I cannot use something like envInject either (multibranch jobs do not provide the option to 'Prepare an environment for the run' as with other jobs)

Goal

I would like to be able to access the server, owner and project fields set in the job config page. Ultimately I could manage with just the project's ssh/http address even.

Is there some clever way of accessing a job's config from within the pipeline?

Thanks for any suggestions!

Reference images

...

ANSWER

Answered 2021-Jan-25 at 19:37

Within the gitlab branch source plugin (and the documentation) you have a lot more information, than just with the normal branch source plugin. there are environment variables for the project like GITLAB_PROJECT_GIT_SSH_URL/GITLAB_PROJECT_GIT_HTTPS_URL for the git source and many more. So far i did not see one for the server, but that would be parse-able our of the URLs.

Within this information, it should be fairly easy to checkout the repository and build it.

As through the process it came clear, that it is needed to also trigger the pipeline manually, and this is normally also possible with variables (not sure about the Remote File plugin). I assume your Jenkinsfile is a groovy script, which opens up a lot of possibilities. You can define variables and use some logic to determine if the env variable or the parameter is used.

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

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

Vulnerabilities

No vulnerabilities reported

Install gitlab-branch-source-plugin

This plugin is still under development. Thus you cannot install it via the Jenkins Update manager yet. Simply download the latest release into the plugins directory of your Jenkins. I'm not sure if the dependencies get installed automatically. If that is not the case, make sure to install these dependencies:.
branch-api 2.0.8
cloudbees-folder 6.0.3
credentials 2.1.13
git 3.0.5
git-client 2.4.0
gitlab-plugin 1.4.5
scm-api 2.1.1
workflow-api 2.12
workflow-cps 2.29
workflow-job 2.10
workflow-multibranch 2.12

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: