[JIRA] (JENKINS-12321) ability to set unique sauce username and api key per job

Daniel Khodaparast created JENKINS-12321:
--------------------------------------------

             Summary: ability to set unique sauce username and api key per job
                 Key: JENKINS-12321
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12321
             Project: Jenkins
          Issue Type: Improvement
          Components: sauce-ondemand
            Reporter: Daniel Khodaparast
            Assignee: Kohsuke Kawaguchi


It would be nice to have the ability to set the username and api key on a per job basis instead of globally.  We have some jobs that need to use different usernames/keys in order to segregate the data for development and metric purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157937#comment-157937 ]

Ross Rowe commented on JENKINS-12321:
-------------------------------------

I'm actually implementing this feature at the moment, I'll let you know when a new version is ready which includes this functionality.

Cheers,

Ross
               

> ability to set unique sauce username and api key per job
> --------------------------------------------------------
>
>                 Key: JENKINS-12321
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12321
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: sauce-ondemand
>            Reporter: Daniel Khodaparast
>            Assignee: Ross Rowe
>
> It would be nice to have the ability to set the username and api key on a per job basis instead of globally.  We have some jobs that need to use different usernames/keys in order to segregate the data for development and metric purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ross Rowe reassigned JENKINS-12321:
-----------------------------------

    Assignee: Ross Rowe  (was: Kohsuke Kawaguchi)
   

> ability to set unique sauce username and api key per job
> --------------------------------------------------------
>
>                 Key: JENKINS-12321
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12321
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: sauce-ondemand
>            Reporter: Daniel Khodaparast
>            Assignee: Ross Rowe
>
> It would be nice to have the ability to set the username and api key on a per job basis instead of globally.  We have some jobs that need to use different usernames/keys in order to segregate the data for development and metric purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JENKINS-12321 started by Ross Rowe.

> ability to set unique sauce username and api key per job
> --------------------------------------------------------
>
>                 Key: JENKINS-12321
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12321
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: sauce-ondemand
>            Reporter: Daniel Khodaparast
>            Assignee: Ross Rowe
>
> It would be nice to have the ability to set the username and api key on a per job basis instead of globally.  We have some jobs that need to use different usernames/keys in order to segregate the data for development and metric purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158066#comment-158066 ]

Ross Rowe commented on JENKINS-12321:
-------------------------------------

Hi, I've built a beta version of the plugin that should support storing of username/api key on the job level (as well as some improvements to the configuration information in general)...the beta is available from https://repository-saucelabs.forge.cloudbees.com/release/org/jenkins-ci/plugins/sauce-ondemand/1.10-SNAPSHOT/sauce-ondemand-1.10-20120123.194335-1.hpi, could you try it out and let me know if there are any problems?

Thanks,

Ross
               

> ability to set unique sauce username and api key per job
> --------------------------------------------------------
>
>                 Key: JENKINS-12321
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12321
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: sauce-ondemand
>            Reporter: Daniel Khodaparast
>            Assignee: Ross Rowe
>
> It would be nice to have the ability to set the username and api key on a per job basis instead of globally.  We have some jobs that need to use different usernames/keys in order to segregate the data for development and metric purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-12321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ross Rowe resolved JENKINS-12321.
---------------------------------

    Resolution: Fixed
   

> ability to set unique sauce username and api key per job
> --------------------------------------------------------
>
>                 Key: JENKINS-12321
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12321
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: sauce-ondemand
>            Reporter: Daniel Khodaparast
>            Assignee: Ross Rowe
>
> It would be nice to have the ability to set the username and api key on a per job basis instead of globally.  We have some jobs that need to use different usernames/keys in order to segregate the data for development and metric purposes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira