Add support for job pools

Commands can now be assigned to an arbitrary job pool and a limit for
the number of concurrently running jobs in such pools can be provided in
a number of ways:
- via the build command line: qbs --job-limits linker:1
- via the settings: qbs config preferences.jobLimit.linker 1
- in a project file: JobLimit {
                         jobPool: "linker";
                         jobCount: 1
                     }
We provide two job pools ourselves with the cpp module: "compiler" and
"linker".

[ChangeLog] Added the concept of job pools for limiting concurrent
execution of commands by type

Task-number: QBS-743
Change-Id: Ib3f361dbc73093e342bf0eba0daf2079a2b3a8ce
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@qt.io>
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>

1 files changed, 16 insertions, 0 deletions

diff --git a/doc/reference/cli/cli-options.qdocinc b/doc/reference/cli/cli-options.qdocinc
index 189a3526a..e6d909963 100644
--- a/doc/reference/cli/cli-options.qdocinc
+++ b/doc/reference/cli/cli-options.qdocinc
@@ -249,6 +249,22 @@
 
 //! [jobs]
 
+//! [job-limits]
+
+    \section2 \c {--job-limits <pool1>:<limit1>[,<pool2>:<limit2>...]}
+
+    Sets pool-specific job limits. See \l{job-pool-howto}{here} for more information on
+    job pools.
+
+    \section2 \c {--enforce-project-job-limits}
+
+    Normally, job limits defined in project files via the \l JobLimit item get overridden
+    by those set on the command line. If this option is passed, they get maximum priority
+    instead. Use it if there are product-specific limits that make more sense for
+    that part of the code base than the generic ones you'd like to apply globally.
+
+//! [jobs]
+
 //! [keep-going]
 
     \section2 \c --keep-going|-k