[
https://issues.apache.org/jira/browse/HIVE-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15562378#comment-15562378
]
Sergio Peña commented on HIVE-14745:
------------------------------------
Option #1 won't have any problem if we move the jenkins job. As you said,
JIRAService will be called immediately after PTestClient finishes on the
jenkins-execute-build.sh, so this won't require a new job nor a new node.
Regarding the build servers time. I created a report to INFRA requesting more
executors for Hive. The label we use for the job is 'Ubuntu', and this label is
shared across many other components.
https://issues.apache.org/jira/browse/INFRA-12737
> Remove jira user/password from profiles by using another command to submit
> results to jira
> ------------------------------------------------------------------------------------------
>
> Key: HIVE-14745
> URL: https://issues.apache.org/jira/browse/HIVE-14745
> Project: Hive
> Issue Type: Sub-task
> Components: Hive, Testing Infrastructure
> Reporter: Sergio Peña
>
> Hive ptest uses some properties files per branch that contain information
> about how to execute the tests.
> This profile includes the user & password to submit the results to JIRA. We
> should get rid of this sensitive information from the profile by moving the
> jira submission task to another command or script executed directly by
> Jenkins.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
