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

Configurable git commands deadline #82

Merged
merged 1 commit into from
Jul 20, 2019
Merged

Configurable git commands deadline #82

merged 1 commit into from
Jul 20, 2019

Conversation

bpineau
Copy link
Owner

@bpineau bpineau commented Jul 20, 2019

  • Start logging early, so we can see whether the application started
  • Expose the git commands timeout as a command line flags (and sets generous defaults)
  • Don't display --help/usage info with hard failures error messages
  • Don't wait for git clone to succeed before hooking health probes listener: it was configured to fail probes early, when the initial clone was failing; but an app logging an error message before exiting makes diagnostics easier than kubelet probes failures.

Closes #81

* Start logging early, so we can see wether the application started
* Expose the git commands timeout as a command line flags (and sets generous defaults)
* Don't display --help/usage info with hard failures error messages
* Don't wait for git clone to succeed before hooking health probes listener: it was configured to fail probes early, when the initial clone was failing; but an app logging an error message before exiting makes diagnostics easier than kubelet probes failures.
@bpineau bpineau merged commit 82fda1e into master Jul 20, 2019
@bpineau bpineau deleted the git-timeout branch July 20, 2019 09:26
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 86.215% when pulling 7acd089 on git-timeout into fdab9c1 on master.

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.

CrashLoopBack with error code 2 and no error message
2 participants