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

Define better DC/OS job names #532

Open
maciesse opened this issue Oct 29, 2020 · 3 comments
Open

Define better DC/OS job names #532

maciesse opened this issue Oct 29, 2020 · 3 comments
Labels
good first issue Good for newcomers

Comments

@maciesse
Copy link

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:
immagine

Possible solution: Use a name that is somehow related with the test.
Something like TESTNAME_STARTTIME_randomvalue shuold be enough.
@maciesse maciesse changed the title Possibility to define DC/OS job names Define better DC/OS job names Oct 29, 2020
@tr1ms
Copy link

tr1ms commented Dec 30, 2020

Hello, I'm a beginner and I'd like to challenge myself to fix this issue. Any insights on how I can fix this?

@enudler
Copy link
Collaborator

enudler commented Dec 31, 2020

hi @gsonly
DC/OS is coming to end of life
I suggest take another issue

@tr1ms
Copy link

tr1ms commented Dec 31, 2020

Okay

@NivLipetz NivLipetz mentioned this issue Jun 21, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@enudler @maciesse @tr1ms