predator
predator copied to clipboard
Define better DC/OS job names
Context: Predator running on DC/OS
Problem: DC/OS job names generated by predator are random so, when looking for the execution log, is tricky to find the correct one.
Example:
Possible solution: Use a name that is somehow related with the test.
Something like TESTNAME_STARTTIME_randomvalue
shuold be enough.
Hello, I'm a beginner and I'd like to challenge myself to fix this issue. Any insights on how I can fix this?
hi @gsonly DC/OS is coming to end of life I suggest take another issue
Okay