Difference between revisions of "Documentation/Nightly/Developers/Build system/SlicerBot"
m (Created page with '= Overview = Each time a task associated to the wiki, repository or bug tracker is automated by the execution of a script on a machine, the ''machine user'' running such script …') |
m (→Git) |
||
| Line 18: | Line 18: | ||
In a nutshell, the steps to configure a ''git machine user'' are: | In a nutshell, the steps to configure a ''git machine user'' are: | ||
| − | * | + | * Generate SSK keys without pass-phrase: |
| + | |||
| + | ssh-keygen -t rsa -C "slicerbot@slicer.org" | ||
* Add the generated <code>id_rsa.pub</code> key to the list of SSH keys associated with [https://github.com/slicerbot slicerbot] user. Each key '''*SHOULD*''' be named <code>slicerbot-<hostname></code>. For example <code>slicerbot-factory-south-ubuntu</code> | * Add the generated <code>id_rsa.pub</code> key to the list of SSH keys associated with [https://github.com/slicerbot slicerbot] user. Each key '''*SHOULD*''' be named <code>slicerbot-<hostname></code>. For example <code>slicerbot-factory-south-ubuntu</code> | ||
| + | * Setup git username and email: | ||
| + | git config --global user.name "Slicer Bot" | ||
| + | git config --global user.email "slicerbot@slicer.org" | ||
= SlicerBots = | = SlicerBots = | ||
Revision as of 07:42, 23 December 2014
Home < Documentation < Nightly < Developers < Build system < SlicerBotOverview
Each time a task associated to the wiki, repository or bug tracker is automated by the execution of a script on a machine, the machine user running such script will be identified as SlicerBot.
Type of SlicerBot
Wiki
This SlicerBot user publishes update on the Slicer wiki. The associated wiki account is UdpateBot
Git
This SlicerBot user can commit changes to a defined subset of Slicer repositories. The associated github account is slicerbot and it can commit changes to all repositories associated with the slicerbot-team in Slicer github organization.
As documented on managing deploy keys Github guide, there are multiple approaches to grant a machine access to a repository. We chose the machine user one.
In a nutshell, the steps to configure a git machine user are:
- Generate SSK keys without pass-phrase:
ssh-keygen -t rsa -C "slicerbot@slicer.org"
- Add the generated
id_rsa.pubkey to the list of SSH keys associated with slicerbot user. Each key *SHOULD* be namedslicerbot-<hostname>. For exampleslicerbot-factory-south-ubuntu
- Setup git username and email:
git config --global user.name "Slicer Bot" git config --global user.email "slicerbot@slicer.org"
SlicerBots
As of 2014-12-23, the machines with SlicerBot accounts are:
- factory
- factory-south-ubuntu
- factory-south-win7
