Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368036 - Non-Committer User to Update Website CVS from build.eclipse.org
Summary: Non-Committer User to Update Website CVS from build.eclipse.org
Status: CLOSED WONTFIX
Alias: None
Product: CBI
Classification: Technology
Component: prototype (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CBI Dummy user CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-06 09:55 EST by Marcel Bruch CLA
Modified: 2017-02-07 10:13 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel Bruch CLA 2012-01-06 09:55:36 EST 
We generated some user and developer documentation as part of our build. We'd like to put this on the webpage automatically after a build changed some of these files. See http://www.eclipse.org/recommenders/docbook/ for an early draft.

A simple approach would be to do a cvs commit after each build with committer id and password stored on the build-server. Given that this is rather insecure, I'd
like to start a discussion on this topic. 

Is there any way how we could update our website frequently/after each build w/o risking to store our committer ids and passwords on any server? I could imagine a special user that has commit access to a certain path in the cvs repository only from a certain server (build.eclipse.org). Is something like that possible?
Comment 1 Frederic Gurr CLA 2017-02-07 10:13:13 EST 
Please reopen if this is still required (5 years later).