Actions
Story #22
closedAs a user, I don't have to manually set the concurrency of my special workers to 1
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
Right now, the workers must be started with the -c 1 flag. It may be possible to detect the concurrency setting of a worker as part of the babysit() process, and it also may be possible to set it to 1. If these things are possible, it would be nice if the babysit() function did that for the user, if at least just to ensure that things are working properly.
Actions
Merge pull request #22 from jortel/entitlement
refs #99 - support repo auth.