Hi,
actually that behaviour can be already emulated by using the Favorite
plugin and its ${FAVORITE_USERS_EMAIL} token. I added that to the global
recipients for all jobs, so anyone that wants to watch a given job just has
to flag it as favorite.
Otherwise, I think the 'read' permission covers exactly what is required
here.
Vincent
2013/8/8 Slide <[email protected]>
> I'm looking at implementing an "Add Watch" feature to the email-ext plugin
> similar to the "Add Watch" in JIRA in relation to [1]. The idea itself is
> not difficult to implement, what I want to get some feedback on is the
> security scope for this feature. What security level do people think should
> be necessary in order to add a watch on a job? I was thinking the minimum
> would be the "read" permission, but I'm not sure that is good enough.
> Please let me know what you think would be a good level of security for
> such a feature.
>
> Thanks,
>
> slide
>
>
> [1] - https://issues.jenkins-ci.org/browse/JENKINS-18567
>
> --
> Website: http://earl-of-code.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" 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 Developers" 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.
