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

DockerHealthCheck.java:47-50: Add DockerHealthCheck to the running... #1057

Closed
alex-palevsky opened this issue Mar 13, 2016 · 5 comments
Closed

DockerHealthCheck.java:47-50: Add DockerHealthCheck to the running... #1057

alex-palevsky opened this issue Mar 13, 2016 · 5 comments

Comments

@alex-palevsky
Copy link
Contributor

Puzzle 1041-7f83dd26 in src/main/java/com/rultor/agents/docker/DockerHealthCheck.java:47-50 has to be resolved: Add DockerHealthCheck to the running SuperAgents. In doing so make sure that Rultor crashes throwing a meaningful exception as soon as DockerHealthCheck#execute throws and exception. #1041 has the details on the motivation behind this agent.... The puzzle was created by Armin Braun on 11-Mar-2016.

If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code.
@alex-palevsky
Copy link
Contributor Author

@original-brownbear attached this issue to milestone "2.0" (let me know if this is wrong)

@alex-palevsky alex-palevsky added this to the 2.0 milestone Mar 13, 2016
@original-brownbear original-brownbear mentioned this issue Mar 19, 2016
Open
@original-brownbear
Copy link
Contributor

@alex-palevsky this is postponed.

@alex-palevsky
Copy link
Contributor Author

@alex-palevsky this is postponed.

@original-brownbear right, I added "postponed" label

@alex-palevsky
Copy link
Contributor Author

@alex-palevsky this is postponed.

@original-brownbear got it, someone else will be assigned soon

@alex-palevsky
Copy link
Contributor Author

@original-brownbear Closing this issue now...

@AbdealiLoKo AbdealiLoKo mentioned this issue Jan 30, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alex-palevsky @original-brownbear