[
https://issues.apache.org/jira/browse/HBASE-21935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16789542#comment-16789542
]
stack commented on HBASE-21935:
-------------------------------
Still at this. Spent time figuring ssh-agent. It was timing out on me after a
few hours (ssh-agent args changed its command-line args in later versions).
Next up, the build would fail about five hours in with a weird assembly error
-- a classes dir was not a 'file' (This may come back) and/or failure to find
artifact unless we first prime the new repo by doing a pre-build. Now I'm at
this weird one:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.6.1:testCompile
(default-testCompile) on project hbase-it: Compilation failure
[ERROR]
/opt/hbase-rm/output/hbase/hbase-it/src/test/java/org/apache/hadoop/hbase/RESTApiClusterManager.java:[250,48]
cannot find symbol
[ERROR] symbol: method readEntity(java.lang.Class<java.lang.String>)
[ERROR] location: variable response of type javax.ws.rs.core.Response
{code}
Passes fine if I build locally.
> Replace make_rc.sh with customized spark/dev/create-release
> -----------------------------------------------------------
>
> Key: HBASE-21935
> URL: https://issues.apache.org/jira/browse/HBASE-21935
> Project: HBase
> Issue Type: Task
> Components: rm
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Labels: rm
> Attachments: HBASE-21935.branch-2.0.001.patch,
> HBASE-21935.branch-2.0.002.patch, HBASE-21935.branch-2.0.003.patch,
> HBASE-21935.branch-2.0.004.patch, HBASE-21935.branch-2.1.001.patch,
> HBASE-21935.branch-2.1.002.patch, HBASE-21935.branch-2.1.003.patch,
> HBASE-21935.branch-2.1.004.patch, HBASE-21935.branch-2.1.005.patch,
> HBASE-21935.branch-2.1.006.patch, HBASE-21935.branch-2.1.007.patch
>
>
> The spark/dev/create-release is more comprehensive than our hokey make_rc.sh
> script. It codifies the bulk of the RM process from tagging, version-setting,
> building, signing, and pushing. It does it in a container so environment is
> same each time. It has a bunch of spark-specifics as is -- naturally -- but
> should be possible to pull it around to suit hbase RM'ing. It'd save a bunch
> of time and would allow us to get to a place where RM'ing is canned,
> evolvable, and consistent.
> I've been hacking on the tooling before the filing of this JIRA and was
> polluting branch-2.0 w/ tagging and reverts. Let me make a branch named for
> this JIRA to play with (There is a dry-run flag but it too needs work...).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
