[
https://issues.apache.org/jira/browse/HIVE-14734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491420#comment-15491420
]
Sergio Peña commented on HIVE-14734:
------------------------------------
{{read -s -p}} will ask you for a password, and it won't show the password on
console. I wanted to get rid of environment variables and use parameters, but I
don't like to pass passwords as parameters, so I used that approach. It is a
common command used on applications that ask for passwords. I used before, and
I wanted to include it here.
In jenkins, we will do this to call the script with a password:
$ echo ${JIRA_API_PASSWORD} | jenkins-build-execute.sh
Jenkins already has a plugin to hide the password on the Jenkins log console.
Regarding the profiles, they will continue working as usual. For instance,
HIVE-14734.1.branch-2.1.patch, HIVE-14734.1.branch-1-mr1.patch, etc. If you use
HIVE-1434.patch, then it will use the default profile that is master-mr2. If no
mr2 or mr1 is passed, then mr2 is used as default too.
> Detect ptest profile and submit to ptest-server from jenkins-execute-build.sh
> -----------------------------------------------------------------------------
>
> Key: HIVE-14734
> URL: https://issues.apache.org/jira/browse/HIVE-14734
> Project: Hive
> Issue Type: Sub-task
> Components: Hive, Testing Infrastructure
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Attachments: HIVE-14734.patch
>
>
> NO PRECOMMIT TESTS
> Currently, to execute tests on a new branch, a manual process must be done:
> 1. Create a new Jenkins job with the new branch name
> 2. Create a patch to jenkins-submit-build.sh with the new branch
> 3. Create a profile properties file on the ptest master with the new branch
> This jira will attempt to automate steps 1 and 2 by detecting the branch
> profile from a patch to test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
