Versioning Infrastructure Michael Mirman - Perforce

More documents

Recommendations

Info

Deployment of maintenance scripts (version 1.0) § “Push” using change-commit trigger: push1 change-commit //depot/p4admin/... "updateRefTree -p %serverport% -c p4serv.p4adm.p00,p4serv.p4adm.t00“ § Comma-separated list defines clients to be updated § § Problem: some clients are on different hosts Attempt to solve it: push2 change-commit //depot/p4admin/... "updateRefTree -p %serverport% -c p4serv.p4adm.p00,p4serv.p4adm.t00:ssh:p4test00“ § Problem: Triggers line is too long and cumbersome 10
Deployment of maintenance scripts (version 1.1) § Leverage spec depot, file spec, and client spec: push3 change-commit //depot/p4admin/... "updateRefTree -p %serverport% -c p4serv.p4adm.p…“ § § § Spec depot contains all client specs § Trigger gets all effective clients p4 files -e //spec/client/p4serv.p4adm.p… p4 print //spec/client/p4serv.p4adm.p… Client specs contain Host § Trigger runs ssh to the given host to update client Problems: § § Sometimes trigger runs for a long time If target host is down, we have no mechanism to update the target area 11
Page 1 and 2: Versioning Infrastructure Michael M
Page 3 and 4: Architecture Overview § ~750 users
Page 5 and 6: Using markup language brokerhost=p
Page 7 and 8: Using configurables § Configurable
Page 9: Maintenance Commands (crontabs) §
Page 13 and 14: Deployment of maintenance scripts (
Page 15 and 16: Deployment of maintenance scripts (
Page 17 and 18: Conclusion 17
Page 19: Q&A Michael Mirman: Michael.Mirman@

Versioning Infrastructure Michael Mirman - Perforce

Create successful ePaper yourself

Delete template?

Save as template?