Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 320151

Summary:	hudsonbuild not part of common group
Product:	Community	Reporter:	Antoine Toulmé <antoine>
Component:	CI-Jenkins	Assignee:	CI Admin Inbox <ci.admin-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	d_a_carver, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Antoine Toulmé

2010-07-16 20:31:21 EDT

It looks like my build cannot copy resulting artifacts to the m2repo. When it finally could after I chmod'ed it to 777, it copied them with ownership of hudsonbuild and the group callisto-dev.

Please make sure hudsonbuild is part of the common group. Can you please run this command too:
chown hudsonbuild:common /shared/common/m2repo -R

Thanks!

Comment 1 Antoine Toulmé

2010-07-16 21:05:20 EDT

I found a workaround by adding a chmod step to my hudson build to give read rights to all.

Comment 2 Antoine Toulmé

2010-07-16 21:12:38 EDT

OK, the hudsonbuild user cannot chmod its own files either apparently, so I'm stuck.

Comment 3 Eclipse Webmaster

2010-07-19 09:46:55 EDT

So /shared/common is a location for committers to install tools(JREs,Ruby, etc) required to complete builds, so the hudsonbuild user should not be creating files there. 

Or am I mis-understanding what your trying to do?

-M.

Comment 4 David Carver

2010-07-19 09:57:22 EDT

(In reply to comment #0)
> It looks like my build cannot copy resulting artifacts to the m2repo. When it
> finally could after I chmod'ed it to 777, it copied them with ownership of
> hudsonbuild and the group callisto-dev.
> 
> Please make sure hudsonbuild is part of the common group. Can you please run
> this command too:
> chown hudsonbuild:common /shared/common/m2repo -R
> 
> Thanks!

Any reason that you can't specify a local repo that resides in your workspace and is only available to your particular job?

I do this for the Maven based builds (I know you are using buildr), as it is also a recommended best practice, and guarantees that the repos don't get polluted or corrupted by other builds adding things you may not expect to be there (i.e. different versions of dependencies if you don't have a tight version range specified).

http://www.sonatype.com/people/2009/01/maven-continuous-integration-best-practices/

Comment 5 Denis Roy

2011-03-10 14:55:05 EST

You can add an ACL to allow hudsonbuild to write to your downloads directory.  We don't encourage this since it may lead to unexpected results, and removes any traceability wrt who put the files there, but it is a possibility.