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

add markJobSuccessful api call #595

Merged
merged 5 commits into from
Mar 28, 2016

Conversation

Califax
Copy link
Contributor

@Califax Califax commented Dec 1, 2015

Add logic in job scheduler to trigger dependencies and Pull out logic for getting new job config with incremented success into method. Add unit tests

…Dependencies in job scheduler to implement. Pull out logic for getting new job config with incremented success into method. Add unit tests
@Califax
Copy link
Contributor Author

Califax commented Dec 18, 2015

#600

@brndnmtthws
Copy link
Member

Looks good, thanks!

@brndnmtthws brndnmtthws merged commit 332a041 into mesos:master Mar 28, 2016
* Method: __PUT__
* Query string parameters: `arguments` - jobname to be marked success
* Example: `curl -L -X PUT chronos-node:8080/scheduler/job/success/request_event_counter_hourly`
* Response: boolean (true or false depending on success of request)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The response is actually a string formatted with: "marked job %s as successful: %b"

It is always 200 OK even if success is false, which basically forces clients of the API to parse the returned string. Returning JSON would simplify parsing, using a different status code would be even better.

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.

3 participants