Confirmed users
1,989
edits
| Line 35: | Line 35: | ||
== Open a bug for buildbot and puppet changes == | == Open a bug for buildbot and puppet changes == | ||
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 go before it can be released into a reconfig. The buildbotcustom and puppet-manifests changes can be released at any time. 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 manchines are running from puppet again | 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 go before it can be released into a reconfig. The buildbotcustom and puppet-manifests changes can be released at any time. 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 manchines 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 your changes. | ||
== Open a bug for graph server changes == | == Open a bug for graph server changes == | ||