jenkins-rest | Java client built on top of jclouds | Continous Integration library

by cdancy Java Version: 1.0.2 License: Apache-2.0

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

kandi X-RAY | jenkins-rest Summary

jenkins-rest is a Java library typically used in Devops, Continous Integration, Spring Boot, Jenkin, Docker, RabbitMQ applications. jenkins-rest has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. However jenkins-rest has 3 bugs. You can download it from GitHub, Maven.

Java client, built on top of jclouds, for working with Jenkins REST API

Support

Quality

Security

License

Reuse

Support

jenkins-rest has a low active ecosystem.

It has 334 star(s) with 153 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 21 open issues and 90 have been closed. On average issues are closed in 152 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-rest is 1.0.2

Quality

jenkins-rest has 3 bugs (0 blocker, 1 critical, 1 major, 1 minor) and 109 code smells.

Security

jenkins-rest has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

jenkins-rest code analysis shows 0 unresolved vulnerabilities.

There are 2 security hotspots that need review.

License

jenkins-rest is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

jenkins-rest releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

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

Installation instructions, examples and code snippets are available.

It has 5679 lines of code, 624 functions and 104 files.

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

Top functions reviewed by kandi - BETA

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

Handles an error response
Parse response message
Add the specified environment - - - vars
Re - set the environment variables
Adds authorization headers to the request
Get the crumb
Infers the default authentication credentials
Attempts to retrieve an external value from the passed system property and environment variables
Binds parameters to request
Applies the specified path to the provided folder
Extracts the location header from the response
New queue item
Create a crumb from response
Applies the given path to a string
Extract errors from a Throwable
Remove key - value pairs
Creates a progressive text from the response
Get the request status from the response
Creates a system info from the given HTTP response object

Get all kandi verified functions for this library.

jenkins-rest Key Features

No Key Features are available at this moment for jenkins-rest.

jenkins-rest Examples and Code Snippets

No Code Snippets are available at this moment for jenkins-rest.

Community Discussions

Trending Discussions on jenkins-rest

How to add more/custom data to be stored in jenkins rest api

QUESTION

How to add more/custom data to be stored in jenkins rest api

Asked 2021-Jan-08 at 05:21

My question is similar to this.

What I want is that when my pipelines run, I want to add some information in the job build so that when a REST API call is made it return existing info as well as info that I added to the job build-

Currently, the info present in this API has information like job names, build number, etc...

...

ANSWER

Answered 2021-Jan-07 at 14:45

If it's just metadata you can use the job description and parse it with Regex using Groovy

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

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

Vulnerabilities

No vulnerabilities reported

Install jenkins-rest

Client's can be built like so:.
Client instances do NOT need to supply the endPoint or credentials as a part of instantiating the JenkinsClient object. Instead one can supply them through system properties, environment variables, or a combination of the two. System properties will be searched first and if not found, will attempt to query the environment.
jenkins.rest.endpoint
jenkinsRestEndpoint
JENKINS_REST_ENDPOINT
jenkins.rest.api.token
jenkinsRestApiToken
JENKINS_REST_API_TOKEN
jenkins.rest.credentials
jenkinsRestCredentials
JENKINS_REST_CREDENTIALS