Thank you, I ended up using the Role plugin for that which was super easy to use. Thanks so much.
On Friday, August 8, 2014 12:09:37 AM UTC+7, Daniel Beck wrote: > > Use (Project-based) Matrix Authorization Strategy and optionally enable > the artifact permission by setting the Java system property > -Dhudson.security.ArtifactsPermission=true > > This way, you can allow users read access to a job, builds, and build > logs, but prevent access to job config, workspace, and archived artifacts. > > On 07.08.2014, at 18:57, Raine Nguyen <[email protected] <javascript:>> > wrote: > > > I need to have a way to protect all the jobs since I do not want to > expose the protected data including the source code after build, but still > allow users to view the build results to check the issues etc. Please let > me know if there is any path I should take. > > > > All suggestions, advice are very appreciated. > > > > Best > > > > Raine > > > > -- > > 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] <javascript:>. > > 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.
