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

Bug 368036

Summary:	Non-Committer User to Update Website CVS from build.eclipse.org
Product:	[Technology] CBI	Reporter:	Marcel Bruch <marcel.bruch>
Component:	prototype	Assignee:	CBI Dummy user <cbi.prototype-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	frederic.gurr
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Marcel Bruch

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

2017-02-07 10:13:13 EST

Please reopen if this is still required (5 years later).