[
https://issues.apache.org/jira/browse/METRON-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15971547#comment-15971547
]
David M. Lyle edited comment on METRON-856 at 4/17/17 7:43 PM:
---------------------------------------------------------------
You can, but you'd have to take out \-T 2C that seemed to be the beginning of
this issue. This seemed like a good compromise- that is, since Ansible will
somewhat treat them as an atomic operation. It runs both together, so you get
the speedup where it can, but do the rpms last. Are you certain that doing a
mvn clean install forces future package calls to use cached snapshot artifacts?
That doesn't seem good to me.
Anyway, longer short answer. I'm good with whatever works. It currently does
not.
was (Author: dlyle):
You can, but you'd have to take out -T 2C that seemed to be the beginning of
this issue. This seemed like a good compromise- that is, since Ansible will
somewhat treat them as an atomic operation. It runs both together, so you get
the speedup where it can, but do the rpms last. Are you certain that doing a
mvn clean install forces future package calls to use cached snapshot artifacts?
That doesn't seem good to me.
Anyway, longer short answer. I'm good with whatever works. It currently does
not.
> Ansible rpm build wipes out prior binary build
> ----------------------------------------------
>
> Key: METRON-856
> URL: https://issues.apache.org/jira/browse/METRON-856
> Project: Metron
> Issue Type: Bug
> Reporter: David M. Lyle
> Priority: Blocker
> Labels: newbie
> Fix For: 0.4
>
>
> The Ansible build currently does a second clean which undoes the build that
> was performed with the HDP-2.5.0.0 profile. The 2nd build task in the
> metron-builder role should look more like:
> bq.{{local_action: shell cd {{ metron_build_dir }}/metron-deployment && mvn
> clean package -DskipTests -P build-rpms}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
