[jira] [Commented] (HELIX-229) hpost-review.sh should update the jira with the reviewboard url

["Kanak Biscuitwala (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HELIX-229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757343#comment-13757343 ] 

Kanak Biscuitwala commented on HELIX-229:
-----------------------------------------

This isn't quite as easy as it is for accessing reviewboard.

Option 1:
1. Include a script to authenticate via OAuth (requires browser access -- a problem for people accessing via ssh without X forwarding)
2. Use the Jira REST API with the OAuth token

Option 2:
1. Wrap the Jira REST API in Python or another language to allow entering and caching passwords
2. Use the wrapper

Option 3:
1. Have everyone grab the Jira command line utilities (or include them with the Helix source)
2. Write a wrapper in Python or another language for jira.sh that allows entering and caching passwords
3. Use the wrapper

I think option 2 is the most reasonable, but in order to cache passwords, people would need the keyring module or something similar, or else a password would be required every time. So the flow would need to be something like:

1. Grab the reviewboard URL
2. Check for python version and fail if too low
3. Check for the keyring module
4. Prompt to install the keyring module if not installed
5. Launch the script:
6. Check if password is in keyring, otherwise prompt for it
7. Add the reviewboard URL as a comment in the Jira.
                
> hpost-review.sh should update the jira with the reviewboard url
> ---------------------------------------------------------------
>
>                 Key: HELIX-229
>                 URL: https://issues.apache.org/jira/browse/HELIX-229
>             Project: Apache Helix
>          Issue Type: Improvement
>            Reporter: Kanak Biscuitwala
>            Assignee: Kanak Biscuitwala
>            Priority: Minor
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira