phabricator-jenkins-plugin | Jenkins plugin to integrate with Phabricator | Plugin library

by uber Java Version: Current License: MIT

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

kandi X-RAY | phabricator-jenkins-plugin Summary

phabricator-jenkins-plugin is a Java library typically used in Plugin, Jenkin applications. phabricator-jenkins-plugin has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has medium support. You can download it from GitHub.

This plugin provides [Phabricator][] integration with [Jenkins][]. It allows Jenkins to report build status and coverage information over Harbormaster (or via comments if Harbormaster is not enabled). [Phabricator]: [Jenkins]:

Support

Quality

Security

License

Reuse

Support

phabricator-jenkins-plugin has a medium active ecosystem.

It has 369 star(s) with 94 fork(s). There are 2419 watchers for this library.

It had no major release in the last 6 months.

There are 35 open issues and 100 have been closed. On average issues are closed in 401 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of phabricator-jenkins-plugin is current.

Quality

phabricator-jenkins-plugin has 0 bugs and 0 code smells.

Security

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

phabricator-jenkins-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

phabricator-jenkins-plugin is licensed under the MIT License. This license is Permissive.

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

Reuse

phabricator-jenkins-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.

phabricator-jenkins-plugin saves you 3924 person hours of effort in developing the same functionality from scratch.

It has 8355 lines of code, 611 functions and 96 files.

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

Top functions reviewed by kandi - BETA

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

Performs prebuild
Queries the topalls for the current branch coverage
Get the coverage provider for the current build
Send HarbProcess result via phiaster
Sets up the environment variables
Fetches a differential ID
Get the credentials for the given credentials
Get the revision ID
Sends the Harbore unit results
Creates a POST request
Sends a HarbMaster message to the Conduitator
Call the Phabricator API of the given action
This method is called after a build is triggered
Gets abort - on - revision id
Get the upstream run of a build
Get a relative path from the given include files
Check if the changed file contains the suffix
Execute the build
Sends a uri as an artifact
Executes postDiff comment action
Performs setup
Record coverage
Checks if the current executor is on Windows
Executes the repository
Compares two CodeCoverageMetrics
Sends the diffusion result

Get all kandi verified functions for this library.

phabricator-jenkins-plugin Key Features

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

phabricator-jenkins-plugin Examples and Code Snippets

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

Community Discussions

Trending Discussions on phabricator-jenkins-plugin

Phabricator + Jenkins: Any ideas of how to get the whole workspace when executing an arc diff?

QUESTION

Phabricator + Jenkins: Any ideas of how to get the whole workspace when executing an arc diff?

Asked 2020-Jan-10 at 15:01

I'm using the plugin from Jenkins for the integration with Phabricator. Everything works perfectly during the integration, but when an arc diff is executed, the only files received on the Jenkins job is the files edited or created by the arc diff. This is a problem when creating microservices and editing files that could potentially affect to other microservices.

Any thoughts on how to get the whole workspace from the repository (hosted also in Phabricator) to be tested, instead of only the diff files?

I've created an issue on the plugin, here is the link:

https://github.com/uber/phabricator-jenkins-plugin/issues/334

...

ANSWER

Answered 2020-Jan-10 at 15:01

Using git plugin and the repository URL, has been quite straightforward: added the URL of the staging area (in my case is the same as the repository) and git credentials (as username/password). The only trick is to indicate which tag we need to test. Since phabricator staging areas uses two tags per diff (phabricator/base/${DIFF_ID} with the base code of the diff and phabricator/diff/${DIFF_ID} with the whole code with the diff applied), i used the following setting:

As result, git plugin will build the code of the whole project with the diff applied.

More information about the integration and the needed variables can be found here: https://github.com/uber/phabricator-jenkins-plugin

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

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

Vulnerabilities

No vulnerabilities reported

Install phabricator-jenkins-plugin

Navigate to https://ci.example.com/configure with your base Jenkins URL in place of "ci.example.com". Navigate to the Phabricator section and click the Add button. ![Add Credentials](/docs/add-credentials.png). From the Kind dropdown, select Phabricator Conduit Key. Enter the base URL for your Phabricator instance in the Phabricator URL field. For example https://phabricator.example.com. Enter a description in the Description field for readability.![Configure Credentials](/docs/configure-credentials.png). Paste the Conduit API token (created in the Phabricator Configuration section) in the Conduit Token field. Click the Add button. Click the Save button.
Navigate to https://ci.example.com/configure with your base Jenkins URL in place of "ci.example.com".
Navigate to the Phabricator section and click the Add button. ![Add Credentials](/docs/add-credentials.png)
From the Kind dropdown, select Phabricator Conduit Key.
Enter the base URL for your Phabricator instance in the Phabricator URL field. For example https://phabricator.example.com.
Enter a description in the Description field for readability.![Configure Credentials](/docs/configure-credentials.png)
Paste the Conduit API token (created in the Phabricator Configuration section) in the Conduit Token field.
Click the Add button.
Click the Save button.

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: