Closed
Bug 1014212
Opened 12 years ago
Closed 12 years ago
Remove the need to create Puppet changes for BuildSlaves*.py.erb, production_config.py and production-master.json
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Assigned: armenzg)
References
Details
Attachments
(1 file)
|
4.13 KB,
patch
|
catlee
:
review+
armenzg
:
checked-in+
|
Details | Diff | Splinter Review |
This allows me not to have to touch various repositories to add a new platform.
In the configs all I have to specify is build_dir_prefix and scheduler_slave_platform_identifier to make it unique.
test-masters passes, dump_masters.sh does not show differences, this should be a no-op and it should work for try and buildapi.
+PLATFORMS['linux64-mulet']['slave_platforms'] = ['ubuntu64_vm']
+PLATFORMS['linux64-mulet']['ubuntu64_vm'] = {
+ 'name': 'Ubuntu Mulet VM 12.04 x64',
+ 'build_dir_prefix': 'ubuntu64_vm_mulet',
+ 'scheduler_slave_platform_identifier': 'ubuntu64_vm_mulet'
+}
Attachment #8426500 -
Flags: review?(catlee)
Updated•12 years ago
|
Attachment #8426500 -
Flags: review?(catlee) → review+
| Assignee | ||
Comment 1•12 years ago
|
||
Comment on attachment 8426500 [details] [diff] [review]
Remove the need for touching puppet when adding a new platform
https://hg.mozilla.org/build/buildbotcustom/rev/00fb5e8f906b
Attachment #8426500 -
Flags: checked-in+
| Assignee | ||
Updated•12 years ago
|
Assignee: nobody → armenzg
Comment 2•12 years ago
|
||
Merged and deployed to production.
| Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•