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.
