Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[TRACKER] Jenkinsfile rework #66

Open
12 of 16 tasks
MrKevinWeiss opened this issue May 15, 2020 · 0 comments
Open
12 of 16 tasks

[TRACKER] Jenkinsfile rework #66

MrKevinWeiss opened this issue May 15, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@MrKevinWeiss
Copy link
Collaborator

MrKevinWeiss commented May 15, 2020 •
edited
Loading

There are a number of improves that should happen with the CI and specifically Jenkinsfile.

  • Make Jenkinsfile declarative as it is better documented and seems to be preferred
  • Run all tests on nodes before releasing them to prevent async behaviour
  • Tune timeouts (total, node_total, per test)
  • Proper error handling
  • Cancel whole job quickly
  • Build on master and only send binaries
    • Master can use build in docker to get binaries
    • Nodes must have a static RIOT folder /opt/RIOT used for flashing and make robot-test
    • Master only unstashes RobotFW and binaries in nodes for tests
  • Only run nodes with unique boards
  • Don't run tests if wiring isn't present
  • Add params to only run selected boards
  • Add params to only run selected applications
  • Add params to run all cpu?
  • Run RIOT tests?
  • Add args for make as parameter
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MrKevinWeiss