Confirmed users
194
edits
ReleaseEngineering: Difference between revisions
→Documentation
| Line 123: | Line 123: | ||
** [[ReleaseEngineering/Deployment|Deployment]] - How we deploy our tools, and how do we update them. | ** [[ReleaseEngineering/Deployment|Deployment]] - How we deploy our tools, and how do we update them. | ||
* [[ReleaseEngineering/OverviewArchitectureDiagram|Overview Architecture Diagram]] - an architecture diagram that gives a high level overview of systems involved in producing releases of Mozilla's software | * [[ReleaseEngineering/OverviewArchitectureDiagram|Overview Architecture Diagram]] - an architecture diagram that gives a high level overview of systems involved in producing releases of Mozilla's software | ||
* [[ReleaseEngineering/Tupperware|Tupperware]] - apps in Docker, great for keeping an unpolluted development environment, testing patches and enabling new contributors to join the effort. | * [[ReleaseEngineering/Tupperware|Tupperware]] - apps in Docker/Vagrant, great for keeping an unpolluted development environment, testing patches and enabling new contributors to join the effort. | ||
Vagrant is used as a quick and easy way to provision the docker apps and make the setup truly plug n' play. The current setup only has a single Vagrantfile which launches BuildAPI and BuildBot, with their dependency apps RabbitMQ and MySQL. | Vagrant is used as a quick and easy way to provision the docker apps and make the setup truly plug n' play. The current setup only has a single Vagrantfile which launches BuildAPI and BuildBot, with their dependency apps RabbitMQ and MySQL. | ||