Difference between revisions of "Documentation/Nightly/Developers/Build system/SlicerBot/SVN2GitHub"
From Slicer Wiki
(Created page with '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…') |
|||
Line 8: | Line 8: | ||
= Details = | = Details = | ||
− | * As detailed [Documentation/Nightly/Developers/Build_system/SlicerBot#Git here], the <code>slicerbot</code> user is pushing changes. | + | * 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>: | * 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> | <pre> | ||
+ | $ cat /Users/kitware/.ssh/config | ||
Host github-slicerbot | Host github-slicerbot | ||
HostName github.com | HostName github.com | ||
Line 18: | Line 19: | ||
IdentityFile ~/.ssh/slicerbot-factory-south | IdentityFile ~/.ssh/slicerbot-factory-south | ||
</pre> | </pre> | ||
+ | |||
* The associated cronjob entry is reported below: | * The associated cronjob entry is reported below: | ||
Line 25: | Line 27: | ||
*/1 * * * * /Volumes/Dashboards/SVN2Github/lockrun --quiet --lockfile=/Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.lockrun -- /bin/sh /Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.sh | */1 * * * * /Volumes/Dashboards/SVN2Github/lockrun --quiet --lockfile=/Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.lockrun -- /bin/sh /Volumes/Dashboards/SVN2Github/Slicer-SVN2GitHub.sh | ||
</pre> | </pre> | ||
+ | |||
+ | |||
+ | * [https://github.com/hilbix/lockrun Lockrun] tool is used to ensure no concurrent rebase&push are occurring. | ||
+ | |||
+ | * |
Revision as of 19:09, 19 October 2015
Home < Documentation < Nightly < Developers < Build system < SlicerBot < SVN2GitHubThis 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 withgithub-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.