Improve ec2 usage tracking (Connect)
We should help Joey get a better idea of what team is making use of ec2 and how much are they using it. The core requirements are to provide:
* stats per-team for jenkins builds (team owning the build, and aggregated time per build/team for a full month)
* google analytics or similar stats to indicate if certain build results are being downloaded at all (google analytics can't help with download stats)
* jenkins ec2 plugin could tag slaves as belonging to a certain class/group, which would help with accounting (nice-to-have)
Blueprint information
- Status:
- Complete
- Approver:
- Joey Stanford
- Priority:
- Low
- Drafter:
- Данило Шеган
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- Accepted for trunk
- Implementation:
-
Unknown
- Milestone target:
-
backlog
- Started by
- Completed by
- Milo Casagrande
Related branches
Related bugs
Sprints
Whiteboard
[danilo 2012-06-08] Setting the priority to 'essential' before the planning call for 2012.06 (so it flows to the top of the backlog list for re-prioritization).
[pfalcon 2012-06-11] I wonder, if this really "Essential" for 12.06. This is of course what we discussed at the Connect session, but as far as I got it, message from Joey was that he's satisfied with the work done with EC2 optimization during 12.04-12.05, and we discuss future nice-to-have features, not something pressing. IMHO, it would be nice to intersperse "accounting" type work with actually fixing identified issues/bottlenecks, e.g. https:/
[danilos, June 22, 2012] Moved to backlog
Meta:
Headline: TBD
Acceptance: TBD
Work Items
Work items for 2012.06:
[pfalcon] Evaluate the requirements and what's needed to implement per-team stats: TODO
