View source for Documentation/4.6/Developers/Build system/SlicerBot/SVN2GitHub

This page describes how the [https://github.com/Slicer/Slicer Slicer GitHub] repository is maintained in sync with the official [http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/ Slicer SVN] repository.

Note that the [https://github.com/SlicerRt/SlicerRT SlicerRT GitHub] repository is maintaining in sync using a similar process.

= Overview =

A cron job running every minutes on <code>[[Documentation/{{documentation/version}}/Developers/Factory#factory-south.kitware|factory-south]]</code> is doing <code>git svn rebase</code> and then force pushing change onto the Slicer github repository.


= Details =

* As detailed [[Documentation/Nightly/Developers/Build_system/SlicerBot#Git|here]], the <code>slicerbot</code> user is pushing changes.


* The <code>slicerbot</code> user SSH key is associated with <code>github-slicerbot</code> hostname adding the following entry into <code>/Users/kitware/.ssh/config</code>:

<pre>
$ cat /Users/kitware/.ssh/config
Host github-slicerbot
  HostName github.com
  User git 
  IdentityFile ~/.ssh/slicerbot-factory-south
</pre>


* The associated cronjob entry is reported below:

<pre>
$ crontab -l
*/1 * * * * /Volumes/Dashboards/SVN2Github/lockrun --quiet --lockfile=/Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.lockrun -- /bin/sh /Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.sh
</pre>


* [https://github.com/hilbix/lockrun Lockrun] tool is used to ensure no concurrent rebase&push are occurring.


* <code>Slicer-SVN2GitHub.sh</code> and <code>Slicer-SVN2GitHub-slicerbot.sh</code> scripts are available on https://gist.github.com/jcfr/da442a017484b7691018

= ChangeLogs =

* 2015/10/19: Updated script adding --force option to address issue reported on [https://github.com/Slicer/Slicer/pull/375#issuecomment-148759758 Slicer/Slicer/pull/375#issuecomment-148759758]
* 2015/10/19: Created this page and added scripts on https://gist.github.com/jcfr/da442a017484b7691018