hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-18147) nightly job to check health of active branches
Date Thu, 13 Jul 2017 21:45:00 GMT

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

Sean Busbey updated HBASE-18147:
    Attachment: HBASE-18147.v1.patch

I've reworked things to use [Jenkinsfile|https://jenkins.io/doc/book/pipeline/jenkinsfile/]
pipelines. Unfortunately, the pipelines are configured per-branch.

attaching a patch that'll work for master/branch-2 and another that will work for branch-1*.

This isn't all bad. At the moment our configs happen to work the same across all branches
(if we used the branch-1 patch everywhere the extra multijdk dir would get ignored like it
does on precommit), but they might not later. For example, if we want to keep which nightly
checks cause failures in version control as we clean things up then this set up works well
(the alternative is per-branch env variables in jenkins).

There are still some things I'd like to tweak over time and some things that I think are bugs
in yetus. But things are working well enough that I think this is ready to go for a test run
on our actual branches.

> nightly job to check health of active branches
> ----------------------------------------------
>                 Key: HBASE-18147
>                 URL: https://issues.apache.org/jira/browse/HBASE-18147
>             Project: HBase
>          Issue Type: Test
>          Components: community, test
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>         Attachments: HBASE-18147.0.patch, HBASE-18147-branch-1.v1.patch, HBASE-18147.v1.patch
> We should set up a job that runs Apache Yetus Test Patch's nightly mode. Essentially,
it produces a report that considers how the branch measures up against the things we check
in our precommit checks.

This message was sent by Atlassian JIRA

View raw message