Documentation/Nightly/Developers/Build system/SlicerBot - Revision history

JChris.FillionR at 18:31, 25 January 2022

2022-01-25T18:31:21Z

2018-03-07T05:53:55Z

SlicerBots

2018-03-07T05:52:44Z

HtmlDoc

2016-09-20T21:40:05Z

HtmlDoc

2016-06-07T20:47:43Z

Packages

2016-06-07T19:41:27Z

2015-10-19T19:44:47Z

UpdateBot typo

2015-10-19T19:17:27Z

2015-10-19T17:42:04Z

Git

2015-04-29T22:12:26Z

@@ Line 11: / Line 11: @@
 == Git ==
-This SlicerBot user can commit changes to a defined subset of Slicer repositories. The associated github account is [https://github.com/slicerbot slicerbot] and it can commit changes to [https://github.com/orgs/Slicer/teams/slicerbot-team/repositories all repositories associated] with the <code>slicerbot-team</code> in [https://github.com/Slicer Slicer] github organization.
+This SlicerBot user can commit changes to a defined subset of Slicer repositories. The associated Github account is [https://github.com/slicerbot slicerbot] and it can commit changes to [https://github.com/orgs/Slicer/teams/slicerbot/repositories all repositories associated] with the <code>slicerbot</code> in the [https://github.com/Slicer Slicer] GitHub organization.
-As documented on [https://developer.github.com/guides/managing-deploy-keys/#machine-users managing deploy keys] Github guide, there are multiple approaches to grant a machine ''access'' to a repository. We chose the ''machine user'' one.
+As documented on [https://docs.github.com/en/developers/overview/managing-deploy-keys#machine-users 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:

@@ Line 69: / Line 69: @@
 = SlicerBots =
-As of 2014-12-23, the machines with SlicerBot accounts are:
+As of 2018-03-07, the machines with SlicerBot accounts are:
 * factory
 * factory-south-ubuntu
-* factory-south-win7
+* metroplex

@@ Line 34: / Line 34: @@
 == HtmlDoc ==
-Every night <code>Slicer-cpp.tar.gz</code> and <code>SlicerWizard.tar.gz</code> are generated on <code>factory-south-ubuntu</code> and pushed on Kitware public web server:
+See https://github.com/Slicer/apidocs.slicer.org#readme
 == Packages ==

@@ Line 34: / Line 34: @@
 == HtmlDoc ==
-Every night <code>Slicer-cpp.tar.gz</code> and </code>SlicerWizard.tar.gz</code> are generated on <code>factory-south-ubuntu</code> and pushed on Kitware public web server:
+Every night <code>Slicer-cpp.tar.gz</code> and <code>SlicerWizard.tar.gz</code> are generated on <code>factory-south-ubuntu</code> and pushed on Kitware public web server:
 * http://public.kitware.com/Slicer-cpp.tar.gz
 * http://public.kitware.com/SlicerWizard.tar.gz

@@ Line 46: / Line 46: @@
 These bots can upload packages on http://slicer.kitware.com/midas3
-Bots able to upload official packages are:
+=== Applications ===
 * [http://slicer.kitware.com/midas3/user/44 Slicerbot Kitware]
 * [http://slicer.kitware.com/midas3/user/465 Slicerbot Perklab]
 = SlicerBots =

@@ Line 41: / Line 41: @@
 * http://slicer.org/doc/html/
 * http://slicer.org/doc/SlicerWizard/
 = SlicerBots =

@@ Line 7: / Line 7: @@
 == Wiki ==
-This SlicerBot user publishes update on the Slicer wiki. The associated wiki account is [[User:UpdateBot|UdpateBot]]
+This SlicerBot user publishes update on the Slicer wiki. The associated wiki account is [[User:UpdateBot|UpdateBot]]
 == Git ==

@@ Line 28: / Line 28: @@
   git config --global user.name "Slicer Bot"
   git config --global user.email "slicerbot@slicer.org"
 == HtmlDoc ==