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

Allow periods in job names #535

Merged
merged 2 commits into from
Sep 10, 2015
Merged

Conversation

carroux
Copy link
Contributor

@carroux carroux commented Aug 25, 2015

job_name_fail

Marathon allows periods in job names, but Chronos rejects jobs with periods in their names. Periods are useful as a delimiter, and there's no obvious reason why they aren't allowed in job names. I updated the regex to allow periods and added a test to check that the job name validation accepts a job name containing periods.

Tests ran and passed.

@keshavdv
Copy link

I'm looking forward to this!

@felixb
Copy link
Contributor

felixb commented Aug 26, 2015

How about /?
I'd love to have the same hierarchy as in marathon.

@mrtyler
Copy link

mrtyler commented Aug 26, 2015

shipit

FWIW @felixb I am in favor of allowing / and a bunch of other standard ascii separator characters but I have no idea if there are constraints the Chronos authors were trying to follow when they decided this regex (and I don't see any comments about it in JobUtils.scala). Maybe one of them will chime in :)

@brndnmtthws
Copy link
Member

Looks great, thanks!

brndnmtthws added a commit that referenced this pull request Sep 10, 2015
@brndnmtthws brndnmtthws merged commit dded172 into mesos:master Sep 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants