On 11 April 2013 10:17, David Aldrich <[email protected]> wrote:
> Hi Stephen**** > > ** ** > > Thanks for your reply.**** > > ** ** > > **Ø **Which plugins are you using?**** > > ** ** > > I have installed:**** > > ** ** > > **· **Credentials Plugin 1.3.1**** > > **· **SSH Credentials Plugin 0.2**** > > ** ** > > From your explanation, as I am only using credentials for SSH login to > slaves by root, I guess I only need ‘System’ credentials. (Note: I am > using svn as well).**** > > ** ** > > So, please can you give me any advice on my situation where I must manage > two credentials having identical names but different passwords? > Click on the Advanced button for each Credential and set the Description. The description (when non-empty) is what should be displayed in the drop-down... if it isn't then that is a bug in the SSH Slaves plugin > **** > > ** ** > > BR**** > > ** ** > > David**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Stephen Connolly > *Sent:* 11 April 2013 10:09 > *To:* [email protected] > *Subject:* Re: Question about Manage Credentials**** > > ** ** > > On 11 April 2013 09:19, David Aldrich <[email protected]> wrote:* > *** > > Hi**** > > **** > > In our Jenkins system, both Windows and Linux slaves use the same > username. However, the Windows password is different to the Linux > password. This means that the credentials plugin shows two credentials > with the same username. **** > > ** ** > > Which plugins are you using?**** > > **** > > **** > > Is this allowed and, if so, how can I differentiate between them?**** > > ** ** > > Well each credentials implementation defines the API for that credentials > type. It may be that we just need to tweak the credentials so that, e.g. > you could add some display label to a credential**** > > **** > > **** > > What is the difference between a ‘Global’ and ‘System’ credential?**** > > ** ** > > Global means that the credential is discoverable by Jobs and the root > Jenkins instance... i.e. Jobs can use those credentials for e.g. SCP of > build artifacts to the machine, Jenkins can use those credentials for > launching a slave on the machine**** > > ** ** > > System means that the credential is only discoverable by the root Jenkins > instance... i.e. Jenkins can use those credentials for launching a slave on > the machine**** > > ** ** > > User scoped credentials (i.e. those that you add to your own identity via > Jenkins » People » your name » Configure) require your Authentication to > access, so should not normally be used by Jobs or the root Jenkins > instance. The initiating use case for User scoped credentials is the > "Deploy Now" functionality in the CloudBees Deployer plugin 4.0+, where a > Job level action displays a screen that allows selecting the credentials to > use for deployment of the application(s) with each of the deployment > engines (e.g. to CloudBees RUN@Cloud, to Google App Engine, to Cloud > Foundry, etc)**** > > ** ** > > As other plugins play catchup with the Credentials API, I would expect > other user initiated actions to allow credentials selection. For example it > could make sense for a Build Parameter to allow selecting a credential of a > specific type to be made available for the build. Thus when you trigger the > build you would have to select the credential to trigger the build with > (which will come from the User scoped credentials of the triggering user > (and where the user is allowed to use Global scoped credentials also, then > the pool of Global scoped credentials of the correct type). That would be > very powerful (but as I think about it, it may require some minor tweaks to > the Credentials API to make it realizable)**** > > **** > > Best regards**** > > **** > > David**** > > **** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > **** > > ** ** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > **** > > Click > here<https://www.mailcontrol.com/sr/xxJP2j8hHG3GX2PQPOmvUnd1S5HUtV8BNSUnfaZgcue65WT!Vnd0fbfWY1HbjLkYg3j5Bxc307MhR!AbTPK7tQ==>to > report this email as spam. > **** > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
