[
https://issues.apache.org/jira/browse/HIVE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15494539#comment-15494539
]
Sergio Peña edited comment on HIVE-14744 at 9/15/16 9:13 PM:
-------------------------------------------------------------
The option to upload a propertiles file may be part of the #5 subtask (Move
profile configuration to Hive code base). The idea is to have a default one,
but if you replace the default with another in the patch, then we can use it. I
think this is good option to have when new branches are created, and we want to
disable/enable some tests for that branch, we just leave the new properties
file into that branch.
was (Author: spena):
The option to upload a propertiles file may be part of the #5 subtask (Move
profile configuration to Hive code base). The idea is to have a default one,
but if you specify one in the patch, then we can use it. I think this is good
option to have when new branches are created, and we want to disable/enable
some tests for that branch, we just leave the new properties file into that
branch.
> 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)
