Difference between revisions of "Documentation/Nightly/Developers/Build system/SlicerBot/SVN2GitHub"

From Slicer Wiki
Jump to: navigation, search
m
Line 32: Line 32:
  
 
* <code>Slicer-SVN2GitHub.sh</code> and <code>Slicer-SVN2GitHub-slicerbot.sh</code> scripts are available on https://gist.github.com/jcfr/da442a017484b7691018
 
* <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

Revision as of 19:24, 19 October 2015

Home < Documentation < Nightly < Developers < Build system < SlicerBot < SVN2GitHub

This page describes how the Slicer GitHub repository is maintained in sync with the official Slicer SVN repository.

Overview

A cron job running every minutes on factory-south is doing git svn rebase and then force pushing change onto the Slicer github repository.


Details

  • As detailed here, the slicerbot user is pushing changes.
  • The slicerbot user SSH key is associated with github-slicerbot hostname adding the following entry into /Users/kitware/.ssh/config:
$ cat /Users/kitware/.ssh/config
Host github-slicerbot
  HostName github.com
  User git 
  IdentityFile ~/.ssh/slicerbot-factory-south


  • The associated cronjob entry is reported below:
$ crontab -l
*/1 * * * * /Volumes/Dashboards/SVN2Github/lockrun --quiet --lockfile=/Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.lockrun -- /bin/sh /Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.sh


  • Lockrun tool is used to ensure no concurrent rebase&push are occurring.


ChangeLogs

Retrieved from "https://www.slicer.org/w/index.php?title=Documentation/Nightly/Developers/Build_system/SlicerBot/SVN2GitHub&oldid=43039"