[
https://issues.apache.org/jira/browse/HIVE-25715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445119#comment-17445119
]
Zoltan Haindrich commented on HIVE-25715:
-----------------------------------------
there are different levels I could think of:
* ugly-duckling:
** just do a dist build and take
packaging/target/apache-hive-4.0.0-SNAPSHOT-bin/apache-hive-4.0.0-SNAPSHOT-bin/
as the nightly build
** this will work; however its version will be 4.0.0-SNAPSHOT
* twisted:
** run a versions:set on the project which will change the versions of the
packages "connected" to the root pom
** this will have more proper versions on the outside; but internally storage
api will run with X-SNAPSHOT
* frankeinstein:
** reconnect the disconnected pom.xml-s to the root and then run a versions:set
** this approach will make storage-api pick up the hive version in these builds
** it might have its own problems because in the original project the pom-s are
disconnected
* gentlemen:
** go into disconnected modules and update the versions for those as well
(storage-api,standalone-metastore,?)
** this will need some script magic since maven cant do these updates correctly
outside
I think I'll go with the "twisted" approach for now - doing the proper one
could probably also reused as some kind of level release automation...the
twisted approach is simple enough to start with and build the infra around it ;
and we can move forward to "gentlemen" later if there is interest in it
> Provide nightly builds
> ----------------------
>
> Key: HIVE-25715
> URL: https://issues.apache.org/jira/browse/HIVE-25715
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
>
> provide nightly builds for the master branch
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
