ReferencePlatforms/How To/Setup a New Reference Platform: Difference between revisions

ReferencePlatforms/How To/Setup a New Reference Platform (view source)

173 bytes added , 30 August 2012

m

Confirmed users

1,989

edits

@@ Line 36: / Line 36: @@
 There are changes needed to buildbotcustom, buildbot-configs and puppet-manifests to support the new platform - example {{bug|777759}}.  The buildbot-configs patch will have to wait to be released until all your testing is complete and the platform is ready to land in a reconfig.  The buildbotcustom and puppet-manifests changes can be landed at any time.
+There are also changed required to enable a platform's tests running to mozilla-central + peers see https://bugzilla.mozilla.org/show_bug.cgi?id=777759#c31 for an example.
 The changes in puppet-manifests repo are changes to the modules/buildmaster/templates/BuildSlaves-tests.py.erb file.  (From rail: the BuildSlaves-tests.py.erb file is in the puppet-manifests repo, but these machines are running from puppet again master).  As well, you'll need to update the secrets.pp.template and secrets.pp on master-puppet1, and replicate these changes to the other masters.  Changes to the puppet-again servers are deployed automatically, changes to the puppet-manifests servers are not. See [[ReleaseEngineering/Puppet/Usage#Deploy_changes]] on how to deploy changes to servers pulling from the old puppet-manifests repo.