[
https://issues.apache.org/jira/browse/HBASE-21935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791893#comment-16791893
]
stack edited comment on HBASE-21935 at 3/13/19 5:09 PM:
--------------------------------------------------------
Stock make_rc.sh doesn't work against tip of branch-2.0. It does this failure:
{code}
09:52:00 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default-cli) on
project hbase-assembly: Failed to create assembly: Error adding file 'or
g.apache.hbase:hbase-common:jar:tests:2.0.6-SNAPSHOT' to archive:
/Users/stack/checkouts/hbase.git/hbase-common/target/test-classes isn't a file.
-> [Help 1]
{code}
... I have to add a 'clean' inline with the site build to get over this hump.
Adding the 'clean' and re-running. Prediction is that I'll then hit this
issue's exception...
This is the 'clean' addition I'm talking of in the above:
{code}
@@ -78,7 +78,7 @@ function build_bin {
MAVEN_OPTS="${mvnopts}" ${mvn} clean install -DskipTests \
-Papache-release -Prelease \
-Dmaven.repo.local=${output_dir}/repository
- MAVEN_OPTS="${mvnopts}" ${mvn} install -DskipTests \
+ MAVEN_OPTS="${mvnopts}" ${mvn} clean install -DskipTests \
-Dcheckstyle.skip=true site assembly:single \
-Papache-release -Prelease \
-Dmaven.repo.local=${output_dir}/repository
{code}
was (Author: stack):
Stock make_rc.sh doesn't work against tip of branch-2.0. It does this failure:
{code}
09:52:00 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.6:single (default-cli) on
project hbase-assembly: Failed to create assembly: Error adding file 'or
g.apache.hbase:hbase-common:jar:tests:2.0.6-SNAPSHOT' to archive:
/Users/stack/checkouts/hbase.git/hbase-common/target/test-classes isn't a file.
-> [Help 1]
{code}
... I have to add a 'clean' inline with the site build to get over this hump.
Adding the 'clean' and re-running. Prediction is that I'll then hit this
issue's exception...
> 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.0.005.patch,
> HBASE-21935.branch-2.0.006.patch, HBASE-21935.branch-2.0.007.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)
