Confirmed users
1,989
edits
ReferencePlatforms/How To/Setup a New Reference Platform: Difference between revisions
ReferencePlatforms/How To/Setup a New Reference Platform (view source)
Revision as of 18:52, 24 August 2012
, 24 August 2012→Open a bug for graph server changes
| Line 39: | Line 39: | ||
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. | 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. | ||
== Open | == Open bugs for graph server changes == | ||
* testing machines and each type of build need graph server changes | * testing machines and each type of build need graph server changes | ||