[
https://issues.apache.org/jira/browse/HIVE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15488535#comment-15488535
]
Siddharth Seth commented on HIVE-14744:
---------------------------------------
I think that's a good list to get started on. Specifically HIVE-14734,
HIVE-14745, HIVE-14746.
Couple of things which I would like to add (short term ptest enhancements), and
these are independent of the goal to run per-branch without changes.
1) Ability to provide a full profile file - which allows users to exclude
specific tests, change how tests are batched, etc.
2) Allow batch-exec.vm and source-prep.vm to be picked up from a path, rather
than the copies present in the initialzied tomcat instance. This would allow
some ptest enahncements without a restart. It also allows for far more advanced
usage. ptest doesn't need to be restricted to Hive only.
> Improve Hive ptest to execute tests per branch automatically and without
> pre-configurations
> -------------------------------------------------------------------------------------------
>
> Key: HIVE-14744
> URL: https://issues.apache.org/jira/browse/HIVE-14744
> Project: Hive
> Issue Type: Task
> Components: Hive, Testing Infrastructure
> Reporter: Sergio Peña
> Assignee: Sergio Peña
>
> This task is meant to improve the way Hive PTest executes all test per branch.
> Currently, when a new branch in Hive is created, someone with admin rights
> needs to create a new job configuration on Jenkins and the PTest server to
> allow tests on this branch.
> We should remove this human interaction from Jenkins and ptest, and allow any
> committer to test their patches on any branch they specify in the file
> attached automatically.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
