[JIRA] Created: (HUDSON-5723) Allow setting arbitrary command line arguments when defining a mercurial executable

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-5723) Allow setting arbitrary command line arguments when defining a mercurial executable

Hudson issues mailing list
Allow setting arbitrary command line arguments when defining a mercurial executable
-----------------------------------------------------------------------------------

                 Key: HUDSON-5723
                 URL: http://issues.hudson-ci.org/browse/HUDSON-5723
             Project: Hudson
          Issue Type: Improvement
          Components: mercurial
         Environment: Hudson ver. 1.342, hg version 1.4.1, Mercurial plugin 1.25
            Reporter: laurie_int
            Assignee: kohsuke


I'd like to pass an arbitrary set of --config aa.bb="ccc ddd" options to mercurial when it clones (or updates) certain remote repositories. In my case, this is to configure ssh to use a particular private key when doing an automated build.

Putting options in the mercurial executable field does not seem to work (can't find executable error).

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Assigned: (HUDSON-5723) Allow setting arbitrary command line arguments when defining a mercurial executable

Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jglick reassigned HUDSON-5723:
------------------------------

    Assignee: jglick  (was: kohsuke)

> Allow setting arbitrary command line arguments when defining a mercurial executable
> -----------------------------------------------------------------------------------
>
>                 Key: HUDSON-5723
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5723
>             Project: Hudson
>          Issue Type: Improvement
>          Components: mercurial
>         Environment: Hudson ver. 1.342, hg version 1.4.1, Mercurial plugin 1.25
>            Reporter: laurie_int
>            Assignee: jglick
>
> I'd like to pass an arbitrary set of --config aa.bb="ccc ddd" options to mercurial when it clones (or updates) certain remote repositories. In my case, this is to configure ssh to use a particular private key when doing an automated build.
> Putting options in the mercurial executable field does not seem to work (can't find executable error).

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5723) Allow setting arbitrary command line arguments when defining a mercurial executable

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138646#action_138646 ]

jglick commented on HUDSON-5723:
--------------------------------

Would be useful to permit this field to be treated as a complete command-line prefix. Of course there are workarounds:

1. Set up ~/.hgrc on the Hudson server.

2. Make a custom shell script which passes your extra params plus normal arguments ('hg --config s.k=v "$@"' for Bourne shell), and pass that as the Hg executable.

> Allow setting arbitrary command line arguments when defining a mercurial executable
> -----------------------------------------------------------------------------------
>
>                 Key: HUDSON-5723
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5723
>             Project: Hudson
>          Issue Type: Improvement
>          Components: mercurial
>         Environment: Hudson ver. 1.342, hg version 1.4.1, Mercurial plugin 1.25
>            Reporter: laurie_int
>            Assignee: jglick
>
> I'd like to pass an arbitrary set of --config aa.bb="ccc ddd" options to mercurial when it clones (or updates) certain remote repositories. In my case, this is to configure ssh to use a particular private key when doing an automated build.
> Putting options in the mercurial executable field does not seem to work (can't find executable error).

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-5723) Allow setting arbitrary command line arguments when defining a mercurial executable

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138656#action_138656 ]

laurie_int commented on HUDSON-5723:
------------------------------------


In my case, I have this situation:
- running as me interactively, I want to use a passworded ssh private key configured to allow pushing to remote. (So option 1 is no good.)
- running as me in hudson, I want to use a non-passworded ssh private key that only allows pulling.

The second workaround would allow this. The main disadvantage is yet another step to set up a development machine.



> Allow setting arbitrary command line arguments when defining a mercurial executable
> -----------------------------------------------------------------------------------
>
>                 Key: HUDSON-5723
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-5723
>             Project: Hudson
>          Issue Type: Improvement
>          Components: mercurial
>         Environment: Hudson ver. 1.342, hg version 1.4.1, Mercurial plugin 1.25
>            Reporter: laurie_int
>            Assignee: jglick
>
> I'd like to pass an arbitrary set of --config aa.bb="ccc ddd" options to mercurial when it clones (or updates) certain remote repositories. In my case, this is to configure ssh to use a particular private key when doing an automated build.
> Putting options in the mercurial executable field does not seem to work (can't find executable error).

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]