stash-pullrequest-builder-plugin | A Jenkins plugin for Building Stash Pull Requests | Plugin library

by nemccarthy Java Version: Current License: Non-SPDX

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

kandi X-RAY | stash-pullrequest-builder-plugin Summary

stash-pullrequest-builder-plugin is a Java library typically used in Plugin, Jenkin applications. stash-pullrequest-builder-plugin has no bugs, it has no vulnerabilities, it has build file available and it has low support. However stash-pullrequest-builder-plugin has a Non-SPDX License. You can download it from GitHub.

[Join the chat at This Jenkins plugin builds pull requests from a Atlassian Stash server and will report the test results as a comment. This plugin was inspired by the GitHub & BitBucket pull request builder plugins.

Support

Quality

Security

License

Reuse

Support

stash-pullrequest-builder-plugin has a low active ecosystem.

It has 68 star(s) with 136 fork(s). There are 9 watchers for this library.

It had no major release in the last 6 months.

There are 25 open issues and 70 have been closed. On average issues are closed in 423 days. There are 16 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of stash-pullrequest-builder-plugin is current.

Quality

stash-pullrequest-builder-plugin has 0 bugs and 0 code smells.

Security

stash-pullrequest-builder-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

stash-pullrequest-builder-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

stash-pullrequest-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

stash-pullrequest-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, examples and code snippets are available.

It has 2052 lines of code, 214 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 stash-pullrequest-builder-plugin and discovered the below as its top functions. This is intended to give you an instant insight into stash-pullrequest-builder-plugin implemented functionality, and help decide if they suit your requirements.

Runs the build
Start a job
Create a GET request
Checks if we should build a build
Called when a build is started
Called when the build has started
Adds parameters to stash
Adds a parameter
Initialize the pull request
Setup the build
Performs a post build operation
Compares the current Pull Request Activity to the target Activity

Get all kandi verified functions for this library.

stash-pullrequest-builder-plugin Key Features

No Key Features are available at this moment for stash-pullrequest-builder-plugin.

stash-pullrequest-builder-plugin Examples and Code Snippets

No Code Snippets are available at this moment for stash-pullrequest-builder-plugin.

Community Discussions

Trending Discussions on stash-pullrequest-builder-plugin

Missing parameter variables after upgrading "Stash Pullrequest Builder Plugin" to version 1.9 of higher

QUESTION

Missing parameter variables after upgrading "Stash Pullrequest Builder Plugin" to version 1.9 of higher

Asked 2019-Jul-11 at 17:00

Last time I've upgraded Stash Pullrequest Builder Plugin to version 1.9 and after that any triggered build has empty parameter list (parameter variables like ${pullRequestId} specified in documentation are not available: https://github.com/jenkinsci/stash-pullrequest-builder-plugin/blob/master/README.md). Now I've tried version 1.10 and have the same issue. With version 1.8 everything is working fine.

1.8:

1.9 / 1.10:

I am using Jenkins in version 2.180 and Git Plugin in version 3.10.0

Maybe some of you experienced the same issue? I would be appreciated for any help.

...

ANSWER

Answered 2019-Jun-27 at 15:08

Jenkins was changed in version 2.3 to disallow adding parameters to a build if they are not declared in the project configuration. The motivation was to prevent a security issue when a project controlled by an attacker invokes another project with arbitrary parameters. Since the parameters are seen as environment variables by the build scripts, the attacker could make the build load an untrusted library. Since its possible for different projects to be controlled by different users and run with different privileges, such behavior would allow the attacker to exploit permissions of a project he or she is not allowed to configure. The issue is known as SECURITY-170.

Stash Pull Request Builder was adding 10 parameters to the build to provide information about the pull request being built. Following the SECURITY-170 implementation, the plugin was changed in version 1.7.0 to pass those values as environment variables as well. Those environment variables are recorded to the build history. They can be viewed if Build Environment Plugin is installed.

Starting with version 1.9, Stash Pull Request Builder plugin removed the old mechanism of passing pull request data through parameters, as it was causing a large number of warnings in the Jenkins log.

The plugin's README.md file has just been updated to use the term "environment variables" to avoid confusion.

If you really need parameters, you can define them for the project. Starting with the next version of the plugin (presumably 1.11), the configured parameters will be populated with the same values that are available through the environment variables.

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

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

Vulnerabilities

No vulnerabilities reported

Install stash-pullrequest-builder-plugin

It is possible to add a post build action that gives the option to post additional information to Stash when a build has been either successful or failed. These comments can contain environment variables that will be translated when posted to Stash. This feature can be used to post for instance a url to the deployed application or code coverage at a successful build and why the build failed like what tests that did not pass.

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: