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

Sean Busbey updated HBASE-20387:
--------------------------------
    Status: Patch Available  (was: In Progress)

-v1 waiting for a complete cycle of runs, but looks like it works
  - includes a patch for HBASE-20979 because we're greatly increasing the 
number of jenkins API requests we make
  - moves all the flaky test related files into a subdirectory of dev-support 
to organize them better
  - turns 'HBase-Find-Flaky-Tests' and 'HBase-Flaky-Tests' into multibranch 
pipelines
  - updates all the job configs to consume the new multibranch pipeline URLs
  - any branch with these changes will get 1) a flaky report, 2) a flaky 
runner, 3) nightly jobs that exclude flaky tests

the patch currently breaks out the removal of the "-per-branch" job suffix in a 
fixup, so it's easier for me to maintain the branch that's testing these things 
on jenkins. it'll be squashed before commit.

this doesn't address the precommit bot because that job is still only defined 
in jenkins configs. it'll need to be updated once this patch lands in order to 
keep excluding flaky tests.

> flaky infrastructure should work for all branches
> -------------------------------------------------
>
>                 Key: HBASE-20387
>                 URL: https://issues.apache.org/jira/browse/HBASE-20387
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Critical
>         Attachments: HBASE-20387.0.patch
>
>
> We need a flaky list per-branch, since what does/does not work reliably on 
> master isn't really relevant to our older maintenance release lines.
> We should just make the invocation a step in the current per-branch nightly 
> jobs, prior to when we need the list in the stages that run unit tests. We 
> can publish it in the nightly job as well so that precommit can still get it. 
> (and can fetch it per-branch if needed)



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

Reply via email to