| Summary: | Read-only filesystem when accessing downloads area | ||
|---|---|---|---|
| Product: | Community | Reporter: | Ralf Sternberg <rsternberg> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ivan |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Ralf Sternberg
Fixed. But strictly speaking Hudson shouldn't be putting stuff in your downloads area. -M. Thanks! We use it Hudson to publish nightly builds. I was wondering if nighly builds should end up in the mirrored space at all, but since I saw that other projects do so as well, I thought it was ok. If you can point me to some better practice, I'm willing to change our build. As long as your nightly jobs are stored in a directory like /N201* or /N-* or have 'nightly' in the file name, it should be fine(those patterns filter what is not mirrored). The rule is essentially: only committers should publish files on download.eclipse.org(for accountability and security). How you achieve that is up to you. -M. |