3 Commits (c924533e4553bb24e3470429d8ae72c91a54eb8a)

Author	SHA1	Message	Date
Eric Tune	53ee76fe1a	Support Work Queue jobs with variable parallelism ... When job.spec.completions is nil, only one task needs to succeed for the job to succeed, and parallelism can be scaled freely during runtime. Added tests. Release Note: This causes two minor changes to the API. First, unset parallelism previously was defaulted to be equal to completions. Now it always defaults to 1 if unset. Second, having parallelism=N and completions unset would previously be defaulted to 1 completion and N parallelism. (this is not something we expect people to do, though) Now, no defaulting occurs in that case, and the job's behavior is different (any completion causes success).	2016-01-22 14:57:51 -08:00
Chao Xu	2b2f285777	run hack/update-generated-docs.sh	2015-12-21 10:41:30 -08:00
Eric Tune	319ebc40ba	Document several patterns for using Job.	2015-12-10 15:54:23 -08:00