Last week we mentioned in a post how Nokia has stopped supporting the Facebook Developer community group where developers get help on development from Nokia experts. This week, Nokia also announced the discontinuation of Nokia Developer Projects Service due to an ongoing trend of low activity and increasing costs. Once this service stops, all unsaved data will be lost.
The Nokia developer’s group is sending out a message to all developers to backup any of their project data as soon as possible. As of now, a date has not been announced for the discontinuation of this service, but they promised it will be in a few weeks. The other community services, including discussion boards and wiki, will remain available for future use.
Nokia Developer Projects is the online hosting solution for collaborative software development in mobile. It is a place where you can explore and grow your idea or join a new project.
Here is a walkthrough on how you can migrate your repositories to another service:
For Git
-
1. Make sure that you have pulled the latest revision of the repository you wish to move. You can usually achieve this by running the following command in your local repository:
git fetch origin
-
Create an empty Git repository on another service of your choice
-
Add the newly created empty repository as a new remote by running the following command:
git remote add new_repo https://$LOCATION_OF_NEW_REPO
-
In the root directory of the repository, run the command:
git push –tags new_repo refs/remotes/origin/*:refs/heads/*
-
You can now clone the new repository and start using it. It should have the entire history of the old one.
For Mercurial
-
Make sure that you’ve pulled the latest revision of the repository you wish to move.
-
Create an empty hg repository on another service of your choice
-
Edit the .hg/hgrc file of the repository you wish to move adding the following line to the [paths] section:
new_repo = https://$LOCATION_OF_NEW_REPO
-
In the root directory of the repository, run the command:
hg push new_repo
-
You can now clone the new repository and start using it. It should have the entire history of the old one.
For subversion
-
Download and install rsvndump on your local machine
-
Create a subversion dump file by running
rsvndump –username $username –password $password –keep-revnums https://$PATH_TO_MULTIPROJECT_REPO > repository.dump
-
(Optional) If you need to filter out some cruft from the repository before importing it somewhere else, this should be done now. The tool svndumpsanitizer is recommended for the job.
-
Set up an empty svn repository on another service of your choice
-
Transfer the dump file to the new server.
-
Import (or have your friendly new system admin import) the dump file by running:
svnadmin load /path/to/new/repo < repository.dump
-
You can now check out the new repository and start using it. It should have the entire history of the old one (minus the stuff you optionally excluded with svndumpsanitizer).
The Nokia Developer group thanks you for using Projects and being part of the community. You can check out other post from the OTEKBITS Developer’s corner here.