and what is the domain specification in each credential domain? If the credentials are all scope System, then it is a bug in the plugin providing the credentials drop down if they show up in a job configuration screen.
If the credential domains have a sufficiently restrictive domain specification then the credentials drop down will narrow its selection as, e.g. the SCM URL is progressively completed. Finally if you install the folders plugin (oh look it's fully [open source]( https://github.com/jenkinsci/cloudbees-folder-plugin/) and [available from the update center]( https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Folders+Plugin)... it only retains the `cloudbees-` prefix because it was the only way we could convince the sales guys to let us open source it ;-) ) then you can have a credential store specific to a folder and thus only jobs within the folder have access to the credentials defined in the folder... So you could have a folder for Project A and a folder for Project B (but that only works if the credentials matter to jobs... if the credentials matter to slaves System scope should have you sorted... and if it doesn't please provide a step by step (assume-dealing-with-an-idiot-style) test case and I will check if there is a bug) On 11 July 2014 09:59, martin flehmig <[email protected]> wrote: > Thanks for your reply and help. > > We updated the credential plugin to version 1.15 like you suggested. > Afterwards, we added a credential domain for each project and added a > credential with scope 'system' to each domain. Nevertheless, user of > project A can use the SSH credentials of slave node from project B. > > How can we see to which system a credential is tied? > > Thanks, > martin > > > Am 10.07.2014 13:00, schrieb Stephen Connolly: > > Fixed in 1.15... Sñr Beck can get the update immediately from the update > > center he uses... if you are not in that club and don't want to wait the > > 8-24h for the OSS update center to pick it up you can download directly > > from http://jenkins-updates.cloudbees.com/download/plugins/credentials/ > > > > > > On 10 July 2014 11:25, Daniel Beck <[email protected]> wrote: > > > >> On 10.07.2014, at 12:03, Stephen Connolly < > [email protected]> > >> wrote: > >> > >>> Credentials for use against slave nodes only should be set to scope > >> SYSTEM... that's what SYSTEM scope is for... > gm>> > >> Each credential should only be available for configuring one specific > >> slave, and not the other slave. Maybe domain restrictions might work > here? > >> > >> -- > >> 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/d/optout. > >> > > > > -- 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/d/optout.
