log the time db patch application takes in developer accessible location
Bug #678289 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Stuart Bishop |
Bug Description
I realise that this is /very close/ to being a duplicate, but I wanted a single clear statement of what we need.
We need to record somewhere where developers can access it, how long each DB patch takes to apply. Recording in a log file that is rsynced to devpad would be fine.
This is important (e.g. before the release in december) because we need this to QA db patches as part of continuous deployment; moving to an incremental fashion there matters because its a prerequisite for safely merging db-devel to devel pre-release - and that matters because the qa toolchain functions better if we keep just one branch deployed.
summary: |
- log in developer accessible location the time db patch application takes + log the time db patch application takes in developer accessible location |
tags: |
added: bad-commit-9997 removed: qa-needstesting |
tags: | added: qa-bad |
tags: | removed: qa-bad |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
Changed in launchpad: | |
milestone: | none → 11.01 |
To post a comment you must log in.
I think Robert is talking about bug 368600, which Stuart closed as Won't Fix. I like this proposed change.