Bugzilla – Full Text Bug Listing
| Summary: | Access to Webtools Admins | ||
|---|---|---|---|
| Product: | Community | Reporter: | David Carver <d_a_carver> |
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams |
| Version: | unspecified | Flags: | david_williams:
review+
|
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 321769 | ||
|
Description
David Carver
I'm fine with Dave having access to webtoolsadmin group, as he helps so much with releng tasks. I would like to hear what the plan is for these area/urls though ... perhaps just a note to wtp-releng to see if there's any comment/feedback from others. Thanks, Done. The best way to 'publish' your builds will probably be the same way you do now. Just login to build.eclipse.org and move the files from /opt/public/jobs/jobname/buildlink to your downloads area. -M. (In reply to comment #1) > I'm fine with Dave having access to webtoolsadmin group, as he helps so much > with releng tasks. > > I would like to hear what the plan is for these area/urls though ... perhaps > just a note to wtp-releng to see if there's any comment/feedback from others. > > Thanks, Will do that this week after I get a chance to take a look at the existing docs, and see how best we can use the new WTP Incubator git repos and release process that is undergoing development there. (In reply to comment #2) > Done. > > The best way to 'publish' your builds will probably be the same way you do now. > Just login to build.eclipse.org and move the files from > /opt/public/jobs/jobname/buildlink to your downloads area. > So /opt/public still is going to be the shared location. Okay. Will work on it later this week. Thanks.
> So /opt/public still is going to be the shared location. Okay. Will work on
> it later this week. Thanks.
Excellent point. Hudson.eclipse.org mounts builds /opt/public partition(in the same location), so you may need to do nothing.
Sorry I'm stuck on the idea the the hudson jobs only write data into their own directories. Eventually I'll remember that they can write somewhere else.
-M.
(In reply to comment #4) > > So /opt/public still is going to be the shared location. Okay. Will work on > > it later this week. Thanks. > > Excellent point. Hudson.eclipse.org mounts builds /opt/public partition(in the > same location), so you may need to do nothing. > > Sorry I'm stuck on the idea the the hudson jobs only write data into their own > directories. Eventually I'll remember that they can write somewhere else. > > -M. Well, when if the job is set to Archive artifacts. It will copy those artifacts back to the Master. But in general one can always use the Hudson RESTful API to get at the latest build artifacts and have hudson Zip the contents. I'm going to be messing with the Xquery-Integration milestone 1 for 0.8M1 this week, so will see what happens. I'm not sure if this is working correctly or not. I tried to create a directory under: /home/data/httpd/download.eclipse.org/webtools/incubator/repository/ for xquery and for vex. However, I get a permission denied error. I would assume that with the appropriate rights set I should be able to create the necessary directories. I'll need read write priveledges to the appropriate directory so that when I run my script to publish and update site, it'll be able to copy the files correctly. Matt can you verify the permissions are set correctly and maybe check what permissions are set on the dirs I'm trying to access. Is there another way I'm supposed to publish items? those directories are owned by "webtools.incubatoradmin" group not "webtoolsadmin". So ... gee, Dave ... you got what you asked for :) [but we didn't know what you wanted :) Matt, et. al, This 'incubator' directory was made long ago, before current procedures were in place, and I know now you try to simplify the number of unix groups, so if you agree, you can remove 'webtools.incubatoradmin' and use 'webtoolsadmin" in its place. As far as I know, it's only this 'incubator' directory that uses it ... and only me and Naci are in that group, and I'm sure we won't care. That'd be better than adding Dave to the 'webtools.incubatoradmin' group and perpetuating the problem. Thanks, (In reply to comment #7) > those directories are owned by "webtools.incubatoradmin" group not > "webtoolsadmin". So ... gee, Dave ... you got what you asked for :) [but we > didn't know what you wanted :) Those darn end users. :)
> so if you agree, you can remove 'webtools.incubatoradmin' and use
> 'webtoolsadmin" in its place.
Done.
-M.
|