We have them for buildbot, buildbot-configs, buildbotcustom but not for tools and mozharness. These repositories are used in production and sometimes we need to land something on default for preproduction testing while the old vesion is still used on production. We should create production branches for any repository that build slaves use, and make sure that our production automation only pulls the production branch.
an example of how this would help is bug 557260. we want to bake that in preproduction now, but if we land the required tools changes, it will break production, so we can't test this code in a full preproduction environment.
We need to update all our factories to update to the production branch of tools.
Product: mozilla.org → Release Engineering
This is made easier by bug 712205.
Component: Other → General Automation
QA Contact: catlee
Whiteboard: [cleanup] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3105] [cleanup]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3105] [cleanup] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3110] [cleanup]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3110] [cleanup] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3115] [cleanup]
I don't think this bug is relevant anymore. We've moved away from the "production" branch model of doing things, and generally deploy things as new versions of packages instead.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.