Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Switching Moodle main code repository to Git: Difference between revisions

From MoodleDocs
Line 3: Line 3:
===Reconfigure CVS server===
===Reconfigure CVS server===
# stop automatic weekly tagging and daily version commits in CVS
# stop automatic weekly tagging and daily version commits in CVS
# take away all CVS write access from main CVS moodle module at cvs.moodle.org (keep all contrib and lang modules unchanged) - only account Petr and Martin can commit manually
# stop automatic cvs.moodle.org --> git.moodle.org export
# stop automatic cvs.moodle.org --> git.moodle.org export
# take away all CVS write access from main CVS moodle module at cvs.moodle.org (keep all contrib and lang modules unchanged) - only moodlerobot and CVS admin will have write access


===Sync CVS with Git===
===Sync CVS with Git===

Revision as of 06:16, 14 December 2010

Necessary changes on moodle.org servers

Reconfigure CVS server

  1. stop automatic weekly tagging and daily version commits in CVS
  2. take away all CVS write access from main CVS moodle module at cvs.moodle.org (keep all contrib and lang modules unchanged) - only account Petr and Martin can commit manually
  3. stop automatic cvs.moodle.org --> git.moodle.org export

Sync CVS with Git

  1. make binary snapshot from git cvshead to CVS HEAD - override CVS checkout with files from current cvshead Git branch

Tweak git://git.moodle.org/moodle.git

  1. give write access to Sam, Petr, Eloy and Martin
  2. set up git commit hooks that push mirrors to Github and Gitorious from git.moodle.org (all 4 branches, we need to set up keys for the moodlerobot)
  3. set up git commit hook that triggers export to CVS commit mirror (all 4 branches, we need to tweak the PHP script and keys for CVS commit access)
  4. create new master branch from cvshead
  5. delete old cvshead branch in Git (the master is the correct name now)

Set up git://git.moodle.org/integration.git

  1. give write access to Sam, Petr, Eloy and Martin
  2. configure Pull project to track this repo

Next steps

  • branch MOODLE_20_STABLE from HEAD in CVS
  • create new MOODLE_20_STABLE branch form master in git
  • set up 3 QA moodle sites on top of the integration git repo
  • create some workflow for amosbot commit requests into /install/xx/

Already done

  • create PULL project for requests