Stamatis Zampetakis created HIVE-28968:
------------------------------------------
Summary: In CI use dedicated project-local .m2 directory for
storing maven artifacts
Key: HIVE-28968
URL: https://issues.apache.org/jira/browse/HIVE-28968
Project: Hive
Issue Type: Improvement
Components: Build Infrastructure
Reporter: Stamatis Zampetakis
Assignee: Stamatis Zampetakis
Currently the maven artifacts are stored under [.git/.m2
directory|https://github.com/apache/hive/blob/aeda0627030ec0bb7d299e38a08eb29860b51173/Jenkinsfile#L100].
In terms of functionality the exact location (.git/.m2 vs .m2) does not
matter. However, putting the artifacts under the .git folder can lead into
confusion and false conclusions for people not very familiar with the
specificities of the CI.
For instance, someone who is not gonna look into detail on what is present
under the .git directory may think that the .git data for the project are huge.
Using commands such as {{du -h --max-depth=1}}, which is also used in [some
places by the
CI|https://github.com/apache/hive/blob/aeda0627030ec0bb7d299e38a08eb29860b51173/Jenkinsfile#L106],
can endorse such false impressions.
Moreover, the .m2 directory is a more common place for storing the maven
artifacts in CI/CD pipelines.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
