On Thu, Aug 8, 2013 at 3:12 PM, Stephen Connolly
<stephen.alan.conno...@gmail.com> wrote:
>
>>
>> Since I'm not using folders I can't think of any way they relate (or
>> should) to credentials.
>
>
> I think you are missing out. Folders are not views. A job belongs to a
> folder. The credentials API will walk up the tree of owners asking them to
> contribute to the list of available credentials. So you can store
> credentials not just at the root, but also in a folder or a sub-folder, or a
> sub-sub-folder.
>
> So instead of having 10 jobs at the root for the FooBar project, you create
> a FooBar folder, grant control to do things in that folder to the team that
> are working on the FooBar project, and let them store the credentials that
> their jobs need to do in their folder.... all scoped nicely
Is the way this is supposed to work documented somewhere? I'm
picturing someone who works on a bunch of different projects having to
enter their credentials more than once.
--
Les Mikesell
lesmikes...@gmail.com
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
