Bug 270633 - Enable read-only access to Hudson
Summary: Enable read-only access to Hudson
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Cross-Project (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 257265
Blocks:
  Show dependency tree
 
Reported: 2009-03-31 12:02 EDT by Andrew Overholt CLA
Modified: 2013-09-13 16:19 EDT (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2009-03-31 12:02:16 EDT 
(Sorry if there's a better component for this)

The recent change to only allow members of callisto-dev to access Hudson has made it impossible for individual committers to see test results, stack traces, etc. so that they can fix them.  Can we please enable read-only access for non-callisto-dev members?
Comment 1 Denis Roy CLA 2009-03-31 12:57:13 EDT 
Does Hudson have the concept of a read-only user and someone who can change everything?
Comment 2 Denis Roy CLA 2009-03-31 12:57:45 EDT 
Moving to cross-project.
Comment 3 Ketan Padegaonkar CLA 2009-03-31 13:07:05 EDT 
Hudson does allow for read only access for general access and r/w access for project members and admins to install plugins, and force builds.

See http://wiki.hudson-ci.org/display/HUDSON/Securing+Hudson for more.
Comment 4 Nicolas Richeton CLA 2009-04-02 04:15:30 EDT 
+1 
Read access will allow committers of other projects (not in callisto-dev) to see how the build works and help them to set up a first build for their projects.
Comment 5 Yves YANG CLA 2009-04-04 03:30:35 EDT 
+1
Comment 6 Denis Roy CLA 2009-04-07 16:31:46 EDT 
I'd like to investigate this soon-ish.
Comment 7 Eclipse Webmaster CLA 2009-04-13 14:06:08 EDT 
Adding dependency to bug 257265.  Once we've the security setup is working the 'anonymous' default user should be the solution here.

-M.
Comment 8 Nick Boldt CLA 2009-04-14 17:10:29 EDT 
(In reply to comment #7)
> Adding dependency to bug 257265.  Once we've the security setup is working the
> 'anonymous' default user should be the solution here.

Seems like the anonymous access is now working due to changes in bug 257265. 

Did some quick test w/ user ebaron from the Linux Tools project; logged in, he can now start/stop builds, comment on them, and explore the workspace. Not logged in, he can still see Hudson's build results.
Comment 9 Eclipse Webmaster CLA 2009-04-15 09:18:09 EDT 
Awesome.  Sounds like we're done here.

-M.