+<p>The release train build is currently never ran automatically.\r
+However, after following all these steps, whenever changes are pushed/merged to <code>release/x.y.z[.w]</code> branch in Gerrit, new Jenkins builds are triggered automatically and they will publish the results (P2 repositories/products) at their designated locations online.</p>\r
+<h4>[Optional reading] Release train build details</h4>\r
+<p>The release train build does two very important steps as the first things,\r
+i.e. build the external dependency P2 repositories for both the\r
+Platform SDK and Simupedia:</p>\r
+<pre><code>stage('External Dependencies') {\r
+ node {\r
+ build job: 'SDK/Deploy External Components to Web', parameters: params1\r
+ build job: 'Member Components/Simupedia/fi.semantum.simupedia.build.p2.site', parameters: params1\r
+ } \r
+}\r
+</code></pre>\r
+<p>After that it builds the Platform SDK and Simupedia before building anything else:</p>\r
+<pre><code>stage('SDK') {\r
+ node {\r
+ build job: 'SDK/Simantics SDK', parameters: params1\r
+ // Note that Simantics SDK builds simupedia-git as well\r
+ }\r
+}\r
+</code></pre>\r