It should be possible to set the checkwatches batch size at the command line
Bug #222019 reported by
Graham Binns
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Low
|
Graham Binns | ||
Bug Description
At the moment it's possible to choose which bugtrackers are to be updated by specifying '-t bugtracker-name' for each bugtracker when running checkwatches.
It should also be possible to set the batch size for run at the command line, e.g. '-b 100' or '--batch-size=100'. We could also remove the batch size limit (--batch-size=0). This would allow us to update a whole bug tracker where necessary (for example if it hasn't been synced in a while due to network issues.
| description: | updated |
| Changed in malone: | |
| status: | New → Confirmed |
| Changed in malone: | |
| importance: | Undecided → Low |
| milestone: | none → 2.2.3 |
| status: | Confirmed → Triaged |
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
| Changed in malone: | |
| milestone: | 2.2.3 → none |
| Changed in malone: | |
| assignee: | nobody → gmb |
| milestone: | none → 2.2.3 |
| status: | Triaged → In Progress |
Revision history for this message
| Björn Tillenius (bjornt) wrote Bug fixed by a commit | #2 |
| Changed in malone: | |
| status: | In Progress → Fix Committed |
| Changed in malone: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Didn't actually intend to target this to 2.2.3, though I might end up fixing it as a way to quickly resolve the problems caused by bug 300634.