[
https://issues.apache.org/jira/browse/HIVE-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555861#comment-15555861
]
Sergio Peña commented on HIVE-14745:
------------------------------------
[~sseth] [~prasanth_j] I investigated this. The jira comment is published at
the end of the test on PTest.java. All JIRA information is read from the
profile file.
I'm thinking about 3 options. Which one do you think is better?
Option #1 (This is preferred as we can separate testing and jira interaction)
- Remove JIRA submission from PTest, and write JIRA comments to a file instead.
- Download the comments file as part of the test results to Jenkins.
- Publish the comments (read from the file) to JIRA from
jenkinks-execute-build.sh (this script will have JIRA user and password).
Option #2 (Don't like this too much as we will send user/password through HTTP
request)
- Send JIRA information to the server through PTestClient parameters.
- PTest will read those values from TestStartRequest, and use them on
JIRAService
Option #3 (Easiest way to do it, but it is another file to manage on the server)
- Store JIRA information on a different properties file stored on the ptest
server.
- PTest will read the properties file and use the values on JIRAService
> 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)
