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

Bug 285251

Summary: [build.eclipse.org] change ownership of files in /opt/users/nebulaBuild
Product: Community Reporter: Nicolas Richeton <nicolas.richeton>
Component: ServersAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Nicolas Richeton CLA 2009-07-31 04:38:59 EDT
I'm moving nebula build directories from one account to another (See bug 285127). 
It seems that I'm not allowed to change ownership of the files.

Could you set the ownership and group of the following files to default (nebulaBuild/users) : 
/opt/users/nebulaBuild/nebula_build/*
/opt/users/nebulaBuild/nebula-builds/*

Thanks
Comment 1 Eclipse Webmaster CLA 2009-07-31 10:22:43 EDT
Done.

-M.
Comment 2 Nicolas Richeton CLA 2009-07-31 10:50:09 EDT
Thanks for changing the ownership. 

I'm reopening the bug because I still have an issue, now with publishing files to download. The technology/nebula directory has group nebulaadmin, which lets nebula committers drop files there. But nebulaBuild does not belong to that group so it can't publish files. 

What is the right option ? 
  - make nebulaBuild a member of nebulaadmin ?
  - set chmod o+w ?
  - chown/chgrp on nebula download ? This will prevent management from committer accounts.

Thanks
Comment 3 Eclipse Webmaster CLA 2009-07-31 11:52:16 EDT
The answer is that you build with the build account, and then you(or another commiter with the required access) move the files from the build location to the downloads area.

-M.
Comment 4 Nicolas Richeton CLA 2009-07-31 13:23:04 EDT
The whole idea is to have latest builds published automatically. I don't feel like logging every day / week to move builds results manually. :)
Comment 5 Denis Roy CLA 2009-07-31 13:35:03 EDT
> The whole idea is to have latest builds published automatically. 

Could you do any better if you were using a remote build server?

You essentially have two options when using build.eclipse.org:

a) Build using your committer ID.  You are then free to tag CVS and write to the downloads area.  However, you cannot share your committer account with anyone else, so this doesn't scale.

b) Build using a generic buildID.  This ID can be shared with fellow committers, but cannot be used to put files in the downloads area nor commit to CVS.  You can, however, use scp and SSH keys for the 'passwordless' access to dev.eclipse.org, making it possible to upload files automatically.
Comment 6 Nicolas Richeton CLA 2009-07-31 16:39:40 EDT
ok,

So I will build with my id, using the home of buildNebula as the working dir.

Thanks
Comment 7 Denis Roy CLA 2009-07-31 17:00:15 EDT
Yep, that should work.. Thanks.