3. Retrieving Output

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 CommandAPIDescription
jobsget http://localhost:8080/jobslist all jobs in the SQLite database.
jobs jobidget http://localhost:8080/jobs?jobid=TEXTlist VU output for jobid.
jobs resultN/Alist all results found in the SQLite database.
jobs timestampN/Alist all timestamps found in the SQLite database.
jobs jobid bmget http://localhost:8080/jobs?jobid=TEXT&bmlist the configured benchmark for the jobid.
jobs jobid dbget http://localhost:8080/jobs?jobid=TEXT&dblist the configured database for the jobid.
jobs jobid deleteget http://localhost:8080/jobs?jobid=TEXT&deletedelete the jobid from the SQLite database.
jobs jobid dictget http://localhost:8080/jobs?jobid=TEXT&dictlist the configured dict for the jobid.
jobs jobid resultget http://localhost:8080/jobs?jobid=TEXT&resultlist the result for the jobid.
jobs jobid statusget http://localhost:8080/jobs?jobid=TEXT&statuslist the current status for the jobid.
jobs jobid tcountget http://localhost:8080/jobs?jobid=TEXT&tcountlist the transaction count for the jobid if the transaction counter was run.
jobs jobid timestampget http://localhost:8080/jobs?jobid=TEXT&timestamplist the timestamp for when the job started.
jobs jobid timingget http://localhost:8080/jobs?jobid=TEXT&timinglist the xtprof timing for the job if time profiling was run.
jobs jobid vuidget http://localhost:8080/jobs?jobid=TEXT&vu=INTEGERlist the output for the jobid for the specified virtual user.
jobs jobid timing vuidget http://localhost:8080/jobs?jobid=TEXT&timing&vuid=INTEGERlist the time profile for the jobid for the specified virtual user.