Excerpt | ||
---|---|---|
|
...
IMPLEMENTED |
Jira | ||||||||
---|---|---|---|---|---|---|---|---|
|
...
As part of the gitbox setup, the repositories can be accessed both via GitHub and gitbox.apache.org . Since there is a strong requirement to cut releases from ASF servers, all pom references will point to gitbox instead of GitHub. Of course, committers are free to use GitHub as a remote for pushing, just releases are affected.
Migrating a module
If an individual repository needs to be migrated, usually because it was missed from the initial migration, the following steps are needed (assuming we need to migrate contrib/scripting/esx
:
Code Block |
---|
$ git clone https://github.com/apache/sling-old-svn-mirror # clone the old svn which will be used as a source for the migration
$ cd sling-old-svn-mirror
$ echo contrib/scripting/esx > repo-candidates.txt # file name is not important, but it's helpful to have the name(s) stores in a central place
$ ./tooling/scm/scripts/migrate-to-git.sh -c < repo-candidates.txt # converts the repositories locally in ../sling-modules/
$ ./tooling/scm/scripts/migrate-to-git.sh -r < repo-candidates.txt # provisions the git repository on github/gitbox . Github permissions take 30-60 minutes to sync, you will not be able to push to this repo immediately
$ cp LICENSE ../sling-modules/sling-org-apache-sling-scripting-esx/ && cd ../sling-modules/sling-org-apache-sling-scripting-esx/ && git add LICENSE && git commit -m 'Added LICENSE file' && cd -
$ ./tooling/scm/scripts/migrate-to-git.sh -p < repo-candidates.txt # after verifying that the repository is writable on github
|
Once the repository is provisioned add it to the sling-aggregator repo by following the instructions from the aggregator README.
Older information
Tools and scripts
...
- [jira] [Created] (SLING-3987) move from Subversion to Git
- moving sling to git
- [git] Which git system do we want to use?
- [git] Please test sample migrated git projects and repo setup
- [git] Whiteboard migration
...