No way to run non-interactively with checkbox-launcher

Bug #1370605 reported by Jeff Lane 
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Next Generation Checkbox (CLI)
Fix Committed
High
Unassigned

Bug Description

previous functionality allowed for non-interactive runs.

This has disappeared since things were moved to launchers via checkbox-launcher.

Essentially, the hyperscale team and a couple groups from OEMs who are using our tools for cert testing in-house have asked for the ability to run from a single command line.

Asking outside OEM engineers to learn and create launcher config files is a no-go. They shouldn't have to edit external config files simply to accomplish the same thing as

plainbox run -w /usr/share/2013.com.canonical.certification\:checkbox/whitelists/smoke.whitelist

we need the ability to do exactly that and have it automatically run a whitelist with no user interaction.

at the minimum, I would like to be able to specify the following options:

specific path to whitelist
secure_id for automatic result submission
log file path
verbosity level for logs

Zygmunt Krynicki (zyga)
Changed in checkbox:
status: New → Confirmed
affects: checkbox → checkbox-ng
Revision history for this message
Jeff Lane  (bladernr) wrote :

Added Michael Reed to follow this. As of now, Hyperscale has completely abandoned use of c-c-s in their testing because of the lack of automated runs.

As stated elsewhere (email) this is also a potential blocker for using this in OCP certifications as well, and has been requested by multiple OEMs who were interested in using our tools in their own testing environments.

Changed in checkbox-ng:
importance: Undecided → High
Revision history for this message
Jeff Lane  (bladernr) wrote :

This was fixed by the fix for lp: #1370616 which addressed some other cli needs.

Changed in checkbox-ng:
status: Confirmed → Fix Committed
Revision history for this message
Jeff Lane  (bladernr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.