[jira] [Commented] (HIVE-14744) Improve Hive ptest to execute tests per branch automatically and without pre-configurations
[ https://issues.apache.org/jira/browse/HIVE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15495036#comment-15495036 ] Siddharth Seth commented on HIVE-14744: --- That'll work well. I'd like to retain an option to provide this as a parameter as well; That allows setting up individual jenkins jobs fixed to a profile, and will not require the properties file to be included with each patch (tests other than hive, and custom jenkins setups). This can be in addition to the existing planned changes. > 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)
[jira] [Commented] (HIVE-14744) Improve Hive ptest to execute tests per branch automatically and without pre-configurations
[ https://issues.apache.org/jira/browse/HIVE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15494539#comment-15494539 ] Sergio Peña commented on HIVE-14744: 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)
[jira] [Commented] (HIVE-14744) Improve Hive ptest to execute tests per branch automatically and without pre-configurations
[ https://issues.apache.org/jira/browse/HIVE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488636#comment-15488636 ] Siddharth Seth commented on HIVE-14744: --- In addition, the option to upload a partial properties file, which overrides values specified in an existing one. e.g. select different branch, select java version, disable certain tests, etc. > 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)
[jira] [Commented] (HIVE-14744) Improve Hive ptest to execute tests per branch automatically and without pre-configurations
[ https://issues.apache.org/jira/browse/HIVE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (HIVE-14744) Improve Hive ptest to execute tests per branch automatically and without pre-configurations
[ https://issues.apache.org/jira/browse/HIVE-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15488136#comment-15488136 ] Sergio Peña commented on HIVE-14744: [~sseth] [~prasanth_j] [~ashutoshc] I created these subtasks so that we can automate ptest without doing manual configurations everytime a new hive version is released. Would you help me identifying other subtasks to do that? Also, do you thing the ones I created are good enough to make this work? > 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)
