Tracker: brainstorming for use cases

[j-rivero]

Brainstorming for future implementations:

User actions

Doctor like feature

Feature that can run a number of checks and info retrieval actions in a system that can diagnose the presence of problems before or after have run the simulator: system wise info, versions of packages, ldd info, detect local installations, inspects env variables, check gpu capabilities, hardware related info, egl capabilities, prime dual gpus configuration,

• gzdev doctor
• gzdev doctor --check-after-run-failed

Jenkins interactions

Reproduce a Linux Jenkins build

• gzdev build.o.o reproduce https://build.osrfoundation.org/view/all/job/_test_foo/12/
• Reproduce Jenkins builds locally #54

Call jenkins from command line using current branch of software

• Stay on ignition-foo developing a branch ign-foo-my-testing-branch
• gzdev build.o.o build --platforms mac,windows
• gzdev build.o.o build --platforms mac,windows --wait-until-finish (blocking call)
  • --> finished jobs with status: mac ok, windows failure

Know the testing status of a branch in jenkins

• Stay on ignition-foo developing a branch ign-foo-my-testing-branch
• gzdev build.o.o info --platforms mac,windows
• gzdev build.o.o info --platforms abi-checker

Retry Jenkins jobs from command line

• Stay on release-tools developing changes
• Run a testing run in Jenkins using _test_job_foo
• gzdev build.o.o info --job test_job_foo
  • Latest build 101. Failure -- CMAKE error <link>
• Change release-tool, commit, push
• gzdev build.o.o build --job test_job_foo --retry --wait-until-finish (blocking call)