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.

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

Introduce $binary evaluate ... --run-id-starts-at $integer as option to start the "run ID" from something other than "1" #403

Open
1 of 3 tasks
zimmski opened this issue Jan 30, 2025 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@zimmski
Copy link
Member

zimmski commented Jan 30, 2025

Please help us keep the number of duplicated issues small. We kindly ask you to add your input to the appropriate issue or PR in case your feature idea is already being tracked.

Problem

When we split up an evaluation in our CI and let multiple CI jobs use the "--run 1" option, we only receive "1" as run IDs.

Solution (optional)

Tasks:

  • Simplify how runs are created for all our code. It seems that this is right now all over the place.
  • Introduce --run-id-starts-at $integer as option to start the run ID from something else than 1. Must be >0.

A scenario like $binary --runs 5 --run-id-starts-at 3 should then produce 3 4 5 6 7 as IDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants