Le 23 nov. 2015 7:33 PM, "Mark Waite" a écrit :
>
> Response in-line.
>
> On Mon, Nov 23, 2015 at 10:41 AM Francois Marot
wrote:
>>
>> Thanks Mark and Stephen for your detailed responses.
>> So in the end, I think that Jenkins has a problem because a user that
can create a job has access to ALL c
On Monday 23 November 2015, Francois Marot wrote:
> Thanks Mark and Stephen for your detailed responses.
> So in the end, I think that Jenkins has a problem because a user that can
> create a job has access to ALL credentials. So by default, any user able to
> create one job may steal any source
Response in-line.
On Mon, Nov 23, 2015 at 10:41 AM Francois Marot
wrote:
> Thanks Mark and Stephen for your detailed responses.
> So in the end, I think that Jenkins has a problem because a user that can
> create a job has access to ALL credentials.
>
I'm not clear why you think that a user tha
Hi there,
Have you asked Cloudbees whether they support that feature as part of the
enterprise version yet?
It might help you
Cheers
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails f
Thanks Mark and Stephen for your detailed responses.
So in the end, I think that Jenkins has a problem because a user that can
create a job has access to ALL credentials. So by default, any user able to
create one job may steal any source code located on a git repo whose
Jenkins has the credenti
You might also review the webinar mentioned at
https://www.cloudbees.com/products/cloudbees-jenkins-platform/team-edition/features/role-based-access-control-plugin
in
case the Cloudbees roles based access control plugin could meet your
needs. I'm pretty sure that plugin requires a Cloudbees Enterp
I've not seen any facility which would allow you to restrict use of a
credential by user. Credentials can be limited so that they are only
visible for certain hosts and/or certain protocols, but not by which users
or roles in the system can reference those credentials when defining a job.
I assum
Hi all,
I need your feedback to know if my Company's requirement is compatible with
Jenkins:
we have many Git repositories.
Some jenkins jobs need to access some git repositories. But some
repositories contain source code more sensible than others, hence the need
for different credentials reg
