Yetus design question

[Peter Vary <pv...@cloudera.com>]

Hi Team,

As working on integrating Yetus to Hive, I come around the following problem:

I run Yetus on a clean machine without compiling the project previously.
This means that the I do not have the original artifacts in my maven repository.
When Yetus test-patch.sh tries to run the compilation on the specific modules which are require modules which are not changed then maven will not find the arifacts, and not able to compile.

I can run a maven clean install on the project, but I am not sure this is the best possible solution.

Could someone help me how this problem solved in other projects? Do they use an initialized repository, or do they compile it themselves?

Thanks,
Peter

Re: Yetus design question

[Allen Wittenauer <aw...@effectivemachines.com>]

> On May 24, 2017, at 6:36 AM, Peter Vary <pv...@cloudera.com> wrote:
> 
> Hi Team,
> 
> As working on integrating Yetus to Hive, I come around the following problem:
> 
> I run Yetus on a clean machine without compiling the project previously.
> This means that the I do not have the original artifacts in my maven repository.
> When Yetus test-patch.sh tries to run the compilation on the specific modules which are require modules which are not changed then maven will not find the arifacts, and not able to compile.
> 
> I can run a maven clean install on the project, but I am not sure this is the best possible solution.
> 
> Could someone help me how this problem solved in other projects? Do they use an initialized repository, or do they compile it themselves?


	Yetus should be running maven install itself very early in a test run (generally right after all the pre-checks).  Is 'mvninstall' not enabled?  Is mvninstall failing?  When I've seen failures, it is usually because there are problems with the dependency DAG that a populated repo won't hit...

Re: Yetus design question

[Peter Vary <pv...@cloudera.com>]

Sorry Allen,

I was not on the list yet so I did not see your answer before. :(
The problem was that I have created the hive_personality which updated personality_modules, but did not add this code:

  if [[ ${repostatus} == branch
     && ${testtype} == mvninstall ]] ||
     [[ "${BUILDMODE}" == full ]];then
    personality_enqueue_module . ${extra}
    return
  fi

So it did not run the mvn to root in the beginning.

Thanks for the help!

Peter

> On May 24, 2017, at 3:36 PM, Peter Vary <pv...@cloudera.com> wrote:
> 
> Hi Team,
> 
> As working on integrating Yetus to Hive, I come around the following problem:
> 
> I run Yetus on a clean machine without compiling the project previously.
> This means that the I do not have the original artifacts in my maven repository.
> When Yetus test-patch.sh tries to run the compilation on the specific modules which are require modules which are not changed then maven will not find the arifacts, and not able to compile.
> 
> I can run a maven clean install on the project, but I am not sure this is the best possible solution.
> 
> Could someone help me how this problem solved in other projects? Do they use an initialized repository, or do they compile it themselves?
> 
> Thanks,
> Peter