Actions
Story #1204
closedAs a developer I can dispatch a task which dispatches with a group_id
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
2.8.0
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
The deliverables for this story include the following:
- Add logic to Task object to inspect kwargs for group_id and add it to the TaskStatus for that task
- Add group_id field to TaskStatus model
- Add new index on group_id for task_status collection
- Update existing tasks API endpoints to exclude TaskStatus documents with
group_id != None
Updated by dkliban@redhat.com over 9 years ago
- Blocks Story #1205: As a developer I can dispatch a task that can dispatch a group of tasks added
Updated by dkliban@redhat.com about 9 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Updated by dkliban@redhat.com about 9 years ago
- Status changed from ASSIGNED to POST
Added by dkliban@redhat.com about 9 years ago
Added by dkliban@redhat.com about 9 years ago
Revision fccda011 | View on GitHub
Adds group_id to TaskStatus model
TaskStatus has a group_id field. The group_id is used to group a set of tasks together. The TaskStatus view selects only TaskStatus documents that don't have a group_id set. The task_id field should only be set when performing parallelized work.
Updated by dkliban@redhat.com about 9 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|fccda011a602e6b82f74fac45ecc79ad0ed4b37b.
Updated by dkliban@redhat.com almost 9 years ago
- Blocks deleted (Story #1205: As a developer I can dispatch a task that can dispatch a group of tasks)
Updated by dkliban@redhat.com over 8 years ago
- Status changed from MODIFIED to 5
Updated by dkliban@redhat.com over 8 years ago
- Status changed from 5 to CLOSED - CURRENTRELEASE
Actions
Adds group_id to TaskStatus model
TaskStatus has a group_id field. The group_id is used to group a set of tasks together. The TaskStatus view selects only TaskStatus documents that don't have a group_id set. The task_id field should only be set when performing parallelized work.
https://pulp.plan.io/issues/1204 closes #1204