permissions

[John Test]

Hello,

I have another question around permissions.

Using ldap authentication.
We want a scenario where only the developer that kicked off the build can see their own builds and no one else.
Is this possible to do?

Thanks

[David Rice]

So, is this your scenario:

- Badri and Jen are on the same team

- Badri commits revision X to repository foo kicking off a run of pipeline bar

- Jen commits revision Y to repository foo kicking off a run of pipeline bar

- Only Badri can see the bar pipeline run for X 

- Only Jen can see the bar pipeline run for Y

If so, then, no, GoCD cannot do that.

I'm curious why you would want that capability.

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Test]

Yes that is the scenario.
ok so I am assuming the normal process is that everyone can see all the builds?

We can do what I mentioned with Jenkins, and its nice as people cannot accidentally do stuff to other people's builds.

Would something else prevent such accidental behavior in GoCD?

Thanks

--
You received this message because you are subscribed to a topic in the Google Groups "go-cd" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/go-cd/Sg_IBYwjQn0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to go-cd+un...@googlegroups.com.

[David Rice]

Well, you can use groups to make certain users view only, but I know that's not what you are asking for. Not that it helps, but in my world view a pipeline run belongs to the team and not to an individual.  

If there are actions that really should only be executed by a certain set of individuals, you should be able to use GoCD's existing RBAC groups and manual gates to implement that.