...
- Miguel Herranz (miguel@midokura.com)
- ... (collaborate and put your name here too
)
Document conventions
Aside typical conventions, these one will be used:
- Personal comments: use superscript and include author name in bold. Example: some text Miguel Herranz: "I think this text is awesome!"
- ...
Goals
The goals of continuous integration are the following:
...
To some extension, the following table should give a hint about what to include in each situation:
| Case | Maximum duration | Commit message format & code style | Build of nuttx and/or apps | Minimal testing | Full testing |
|---|---|---|---|---|---|
| Rebase from master in local developer environment | ~1-5 minutes | always | always | optional | not recommended |
| Prepare local code for pull request | ~1 hour | always | always | recommended | optional |
| Continuous integration triggered by a pull request update | ~2-3 hours | always | always | always | optional |
| Nightly build | ~12 hours | always | always | always | always |
Pipeline
The pipeline term is used here in a loose way. It means whatever arrange of tools and scripts to execute the CI. Specifically it does not restrict to the Jenkins CI pipelines.
...
Here is a draft of what could be the pipeline script:
|
|---|
TODO
This is a TODO list with questions and issues to discuss:
...