Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Babel / Large Contribution Import Process"

Line 22: Line 22:
 
# 'run' the above file using wget: wget http://babel.eclipse.org/babel/import_XXXX_zip.php  <-- file name fudged to avoid crawlers
 
# 'run' the above file using wget: wget http://babel.eclipse.org/babel/import_XXXX_zip.php  <-- file name fudged to avoid crawlers
 
# Check the translations using the http://babel.eclipse.org/babel/recent.php
 
# Check the translations using the http://babel.eclipse.org/babel/recent.php
 
+
# Delete the import script: rm /home/data/httpd/babel.eclipse.org/babel/html/import_translation_zip.php
 +
# Delete the translation files.
  
 
Note: If a contributions crosses many projects, such as those from the JapanWG, simply delete the following line in the SQL statements (there are currently two occurrences of this line) :
 
Note: If a contributions crosses many projects, such as those from the JapanWG, simply delete the following line in the SQL statements (there are currently two occurrences of this line) :
  
 
     AND F.project_id = '" . $PROJECT_ID . "' AND F.version = '" . $VERSION . "'
 
     AND F.project_id = '" . $PROJECT_ID . "' AND F.version = '" . $VERSION . "'

Revision as of 15:16, 17 November 2008

This document describes the process the Babel committer uses to import large contributions into the Babel server.

Submitting such a contribution is documented here: http://www.eclipse.org/babel/development/large_contributions.php

Preparation

  1. Make sure the contribution follows the spec, and that is has been approved by Eclipse Legal by submitting it to IPZilla
  2. Unzip the file to babel.eclipse.org:/tmp/tmp-babel/import
  3. Inspect some files in each language to ensure they are properly encoded. Run/hack convertiso.sh as needed.

Import on Staging

  1. su - genie
  2. copy the CVS version of import_translation_zip.php to the STAGING web root: cp /home/data/httpd/babel.eclipse.org/staging/classes/export/import_translation_zip.php /home/data/httpd/babel.eclipse.org/staging/html/import_translation_zip.php
  3. Edit /home/data/httpd/babel.eclipse.org/staging/html/import_translation_zip.php to ensure the target project_id and version are set (see note, below)
  4. 'run' the above file using wget: wget http://babel.eclipse.org/staging/import_XXXX_zip.php <-- file name fudged to avoid crawlers
  5. Check the translations using the http://babel.eclipse.org/staging/recent.php


Import on Live

  1. su - genie
  2. copy the STAGING version of import_translation_zip.php to the LIVE web root: cp /home/data/httpd/babel.eclipse.org/staging/html/import_translation_zip.php /home/data/httpd/babel.eclipse.org/babel/html/import_translation_zip.php
  3. 'run' the above file using wget: wget http://babel.eclipse.org/babel/import_XXXX_zip.php <-- file name fudged to avoid crawlers
  4. Check the translations using the http://babel.eclipse.org/babel/recent.php
  5. Delete the import script: rm /home/data/httpd/babel.eclipse.org/babel/html/import_translation_zip.php
  6. Delete the translation files.

Note: If a contributions crosses many projects, such as those from the JapanWG, simply delete the following line in the SQL statements (there are currently two occurrences of this line) :

   AND F.project_id = '" . $PROJECT_ID . "' AND F.version = '" . $VERSION . "'

Back to the top