[
https://issues.apache.org/jira/browse/HBASE-20387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16576765#comment-16576765
]
Sean Busbey commented on HBASE-20387:
-------------------------------------
messing with this on a branch has convinced me that it can't be a part of the
current nightly job. jobs that consume the include/exclude list we generate
should be robust to failures (like if docker changes behavior). That means they
ought to get artifacts off of the "last success build" URL. incorporating the
report into the nightly job means that if any part of our nightly test suite
fails, all the various test jobs will be stuck consuming an old flaky report
thus missing information about a test that caused nightly to fail.
doing this as multibranch pipeline job(s) still makes sense, they'll just need
to be new ones.
> 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
>
> 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)
