You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/03/17 19:47:00 UTC

[jira] [Updated] (HBASE-24003) Provide a harness for running test-patch locally

     [ https://issues.apache.org/jira/browse/HBASE-24003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Dimiduk updated HBASE-24003:
---------------------------------
    Summary: Provide a harness for running test-patch locally  (was: Provide a test harness for running test-patch locally)

> Provide a harness for running test-patch locally
> ------------------------------------------------
>
>                 Key: HBASE-24003
>                 URL: https://issues.apache.org/jira/browse/HBASE-24003
>             Project: HBase
>          Issue Type: Task
>          Components: build, test
>            Reporter: Nick Dimiduk
>            Priority: Major
>
> This is more of brainstorm or wish than prescriptive. It would be really nice to be able to run locally Yetus {{test-patch}} the way we do for PreCommit and Nightly jobs. There are two use-cases I have in mind. It would be useful for folks who want to hack on the build infrastructure without "doing it live". It would also be handy just for running precommit or nightly checks locally, without waiting for shared resources or polluting the public space with experiments.
> I imagine a new dev-support tool that uses docker or vagrant to spin up the environment in a way that mimics the Jenkins build pipeline as close as possible. Maybe even uses the {{Jenkinsfile}}s directly with something like [jenkinsfile-runner|https://github.com/jenkinsci/jenkinsfile-runner].



--
This message was sent by Atlassian Jira
(v8.3.4#803005)