Description
In HBASE-24280, we investigated a test failure which was ultimately caused by the simultaneous activation of the (intended mutually exclusive) hadoop-2 and hadoop-3 profiles.
After master has moved to only supporting profile activation via the profile itself (rather than a system property) with the removal of the hadoop-2 profile, the build was inadvertently broken as all branches (or is it just 2.x branches and master?) use the one build/yetus scripts in dev-support.
To make sure that these scripts continue to work against all branches, we need to have a clear decision on how profile activation is expected to work in our HBase build. Otherwise, we'll come back to this problem where each branch does things ever-so-slightly different, requiring a bunch of if branch-2; else if branch-2.2; else if branch-2.3 type changes to our yetus scripts.
Attachments
Issue Links
- relates to
-
HBASE-24280 Hadoop2 and Hadoop3 profiles being activated simultaneously causing test failures
-
- Resolved
-