We do this, i.e. we let Hudson upload to download.eclipse.org. The
trick is to manage your acl's (see getfacl/setfacl). The
downloads/tools/buckminster folder looks like this:
thallgren@build:~/downloads/tools/buckminster> getfacl .
# file: .
# owner: thallgren
# group: tools.buckminster
user::rwx
user:hudsonBuild:rwx
group::rwx
mask::rwx
other::r-x
HTH,
Thomas Hallgren
On 2011-01-31 21:13, David Carver wrote:
Unfortunately, the Web Masters won't allow Hudson to upload or
write to those directories. Answer always comes back as security
concerns and tracking.
Dave
On 01/31/2011 02:31 PM, Andreas Hoegger wrote:
I faced the following issue:
The Scout build is fully automated including the upload to download.eclipse.org. The hudson build is running under the 'hudsonBuild' user. Since the 'hudsonBuild' user is not in the project user-group nor any kind of a superuser the upload ends with a permission denied error.
Does anybody has an idea how to upload the build without changing the parent directory on the build server to full access (chmod 777)?
Best regards
Andreas
______________________________________________________
BSI Business Systems Integration AG
Andreas Michael Hoegger
Eclipse Scout Project Lead
Täfernstrasse 16a
CH-5405 Baden
business (direct): +41 (0)56 484 16 87
mobile: +41 (0)78 615 29 29
mail: andreas.hoegger@xxxxxxxxx
web: www.bsiag.com
Meet me at:
- EclipseCon 2011 Santa Clara, California 2011 March 21 - 24 (http://www.eclipsecon.org/2011)
______________________________________________________
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
