[ 
https://issues.apache.org/jira/browse/HBASE-21432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696270#comment-16696270
 ] 

Allen Wittenauer edited comment on HBASE-21432 at 11/23/18 5:13 PM:
--------------------------------------------------------------------

The Github Pull Request Builder has been mostly replaced by the Github Branch 
Source Plugin (which is what I meant above).  The big gotcha is that gprb is 
for freestyle jobs, gbsp is for pipeline jobs.

Using Jenkins w/a Multibranch Pipeline + Github Branch Source Plugin, it 
enables a tab-based system that allows one to re-run branches, PR, and, if 
enabled, tags on demand from the Jenkins UI.  The Yetus integration that is 
done as part of YETUS-681 (and committed into my dev branch) just makes 
test-patch smarter to know it is running under Jenkins, where the PR is at, 
etc., so that there isn't a need to manually configure or pass parameters for 
details that Jenkins itself shares via environment variables.  This means that 
one stanza in the Pipeline can do both full builds and incremental/PR builds 
with no work required in the Pipeline to figure out what type of run it is.


was (Author: aw):
The Github Pull Request Builder has been mostly replaced by the Github Branch 
Source Plugin (which is what I meant above).  The big gotcha is that gprb is 
for freestyle jobs, gbsp is for pipeline jobs.

Using Jenkins w/a Multibranch Pipeline + Github Branch Source Plugin, it 
enables a tab-based system that allows one to re-run branches, PR, and, if 
enabled, tags on demand from the Jenkins UI.  The Yetus integration that is 
done as part of YETUS-708 (and committed into my dev branch) just makes 
test-patch smarter to know it is running under Jenkins, where the PR is at, 
etc., so that there isn't a need to manually configure or pass parameters for 
details that Jenkins itself shares via environment variables.  This means that 
one stanza in the Pipeline can do both full builds and incremental/PR builds 
with no work required in the Pipeline to figure out what type of run it is.

> [hbase-connectors] Add Apache Yetus integration for hbase-connectors 
> repository 
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-21432
>                 URL: https://issues.apache.org/jira/browse/HBASE-21432
>             Project: HBase
>          Issue Type: Task
>          Components: build, hbase-connectors
>    Affects Versions: connector-1.0.0
>            Reporter: Peter Somogyi
>            Priority: Major
>
> Add automated testing for pull requests and patch files created for 
> hbase-connectors repository. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to