Skip to content

Instantly share code, notes, and snippets.

@gctucker

gctucker/kci_data-ideas.md

Created June 26, 2020 12:05
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gctucker/46e704ddbffa2ee806ec8793ff144449 to your computer and use it in GitHub Desktop.
Save gctucker/46e704ddbffa2ee806ec8793ff144449 to your computer and use it in GitHub Desktop.
Download ZIP
kci_data ideas
Raw
kci_data-ideas.md

Like all the other kci_* tools in kernelci-core, kci_data is using a YAML configuration file to know about databases where to send KernelCI data. This is typically going to be db-configs.yaml, with entries such as this:

db_configs:
  api.staging.kernelci.org:
    type: kernelci-backend
    url: https://api.staging.kernelci.org/

The type (or type) is used to determine the code in kernelci-core that will be handling the communication with the database. Typically, that's going to be kernelci-backend initially and ideally kcidb if possible. Others may be added later, with the aim to not have to change the user interface.

To send data on the command line, users would need to at least choose a database and provide the data. For example:

kci_data submit --config=api.staging.kernelci.org results.json

Other sub-commands could be added, to read back some data or enumerate the available database configurations.

Initially, API tokens would need to be passed via command line arguments or the environment. This is fine for most pipeline systems like Jenkins, but having a configuration file would help for manual usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment