kci-dev possible roadmap

[CamilaAlvarez]

Trying to match what the dashboard offers I believe we can follow these steps (I listed the features in a decreasing priority order):

1. Add kci-dev issues command, with the following subcommands:
   1.1 kci-dev issues --origin <origin> that lists all issues from origin.
   1.2 kci-dev issues details --id <id> gives detailed information of the issue with id. It supports multiple --id options.
   1.3 kci-dev issues tests --id <id> lists all the tests related to the issue with id. It supports multiple --id.
   1.4 kci-dev issues build --id <id> lists all builds related to the issue with id. You can query multiple issues using multiple --id options.
2. Add kci-dev hardware command:
   2.1 kci-dev hardware list --origin <origin> that lists all available hardware for origin.
   2.2 kci-dev hardware summary --id <id> gives a summary on the builds, boots and tests run of the hardware with id.
   2.3 kci-dev hardware boots --id <id> lists the boots for the hardware with id. The response is similar to kci-dev results boots.
   2.4 kci-dev hardware builds --id <id> lists the builds for the hardware with id. The response is similar to kci-dev results builds.
   2.5 kci-dev hardware tests --id <id> lists the tests for the hardware with id. The response is similar to kci-dev results tests.
3. Add kci-dev results issues subcommand. We can obtain this information via api/tree/{commit}/full, however, it would be best if there was a api/tree/{commit]/issues available, since full retrieves information we would just discard.
4. Add more options to kci-dev results boots --filter YAML filter. The new options could be: config, compiler, architecture.
5. Modify kci-dev results --arch option. It could allow filtering by various architectures by supporting multiple --arch.

Please let me know how this looks to you.

[padovan]

Hi @CamilaAlvarez! this looks great!

I'll add some comments..

1. kci-dev issues should be kci-dev results issues actually. So you can fold item 3. into this one. You can file a issue on dashboard to create api/tree/{commit]/issues. But there is also an api for all issues now. That being said, I'd place the issues work with lower priority compared to the other items in the roadmap.

2. kci-dev hardware should be kci-dev results hardware. The commands make sense. Instead of --id I'd do --name for plateform name and --compatibles for a compatible list.

3. and 5.: Sound great!

Extra items: #136 #137 (and the same for individual boot).

[padovan]

I just realized we don't have the boot command. We did build and test, but nothing for individual boot commands. Created #164 for that.