[
https://issues.apache.org/jira/browse/HIVE-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556759#comment-15556759
]
Siddharth Seth commented on HIVE-14745:
---------------------------------------
[~spena] - I think you've summarized this nicely. Option#1 is the cleanest, and
easiest to manage, but a little more effort. I'm assuming this will invoke the
JiraService class from the jenkins script.
Option #3 is much quicker though - so it just comes down to time.
Option#1 requires access to jenkins to modify whatever is required. Would this
be a problem if we move to a custom jenkins job again (Apache build servers
take a long time - jobs are in the queue waiting for executors for the longest
time). Option#3 requires access to the node.
> 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)
