The key difference from the standard CLI is the addition of the jobs command. job can also be used as an alias for jobs. All build and tests are assigned a jobid and the associated output is stored in the SQLite database. The jobs command can then be used to retrieve information about any particular job.
Table 10.1. Jobs commands
CLI Command | API | Description |
---|---|---|
jobs | get http://localhost:8080/jobs | list all jobs in the SQLite database. |
jobs jobid | get http://localhost:8080/jobs?jobid=TEXT | list VU output for jobid. |
jobs result | N/A | list all results found in the SQLite database. |
jobs timestamp | N/A | list all timestamps found in the SQLite database. |
jobs jobid bm | get http://localhost:8080/jobs?jobid=TEXT&bm | list the configured benchmark for the jobid. |
jobs jobid db | get http://localhost:8080/jobs?jobid=TEXT&db | list the configured database for the jobid. |
jobs jobid delete | get http://localhost:8080/jobs?jobid=TEXT&delete | delete the jobid from the SQLite database. |
jobs jobid dict | get http://localhost:8080/jobs?jobid=TEXT&dict | list the configured dict for the jobid. |
jobs jobid result | get http://localhost:8080/jobs?jobid=TEXT&result | list the result for the jobid. |
jobs jobid status | get http://localhost:8080/jobs?jobid=TEXT&status | list the current status for the jobid. |
jobs jobid tcount | get http://localhost:8080/jobs?jobid=TEXT&tcount | list the transaction count for the jobid if the transaction counter was run. |
jobs jobid timestamp | get http://localhost:8080/jobs?jobid=TEXT×tamp | list the timestamp for when the job started. |
jobs jobid timing | get http://localhost:8080/jobs?jobid=TEXT&timing | list the xtprof timing for the job if time profiling was run. |
jobs jobid vuid | get http://localhost:8080/jobs?jobid=TEXT&vu=INTEGER | list the output for the jobid for the specified virtual user. |
jobs jobid timing vuid | get http://localhost:8080/jobs?jobid=TEXT&timing&vuid=INTEGER | list the time profile for the jobid for the specified virtual user. |