Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Search CVS, Release Notes, & Build News"

m (Search CVS Release Notes Build News moved to Search CVS, Release Notes, & Build News)
m (Setup Search CVS Tool)
Line 7: Line 7:
 
Read this: http://wiki.eclipse.org/index.php/Search_CVS#Setup
 
Read this: http://wiki.eclipse.org/index.php/Search_CVS#Setup
  
That'll get you a database with search CVS data, but no releases (an empty table). To get Release data, you need to publish RSS feeds for your project(s).
+
That'll get you a database with search CVS data, but no releases (an empty table). To get Release data, you need to publish [[Eclipse_Build_Available_RSS_Feeds_Getting_Started | RSS feeds]] for your project(s).
  
 
== Ensure Regular Updates ==
 
== Ensure Regular Updates ==

Revision as of 19:24, 13 December 2006

So you want to implement Search CVS, generate your Release Notes from that database, and provide a ticker listing builds released on your homepage?

Well, here's how to do that.

Setup Search CVS Tool

Read this: http://wiki.eclipse.org/index.php/Search_CVS#Setup

That'll get you a database with search CVS data, but no releases (an empty table). To get Release data, you need to publish RSS feeds for your project(s).

Ensure Regular Updates

The second part is to ensure that updates are done regularly. I've got a cron running that looks like this:

00 04,20 * * * /shared/modeling/searchcvs/parsecvs.sh 2>&1 1> /shared/modeling/searchcvs/parsecvs_cron.log.txt

Updating the entire database takes about two hours for the projects listed in the setup.sh script.

Restricted Access (Read-Write)

  • A web interface to kick an update to the database (as used in the above script). This isn't restricted yet since too many updates don't cause any problems except to slow down those updates.
  • A web interface to allow authorized users to remove a release from the releases table. The removed release must ALSO be removed manually from the RSS feed or it will be added back after the next database refresh. In theory, this tool should never be needed.

Public Web Access (Read-Only)

Accessing the database is done in three ways:

Back to the top