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

Consider moving e2e cluster tests into this repo #66

Closed
hjacobs opened this issue Nov 1, 2016 · 0 comments
Closed

Consider moving e2e cluster tests into this repo #66

hjacobs opened this issue Nov 1, 2016 · 0 comments
Assignees

Comments

@hjacobs
Copy link
Contributor

hjacobs commented Nov 1, 2016

I think it would make sense to have everything regarding the cluster lifecycle in one repo, i.e. including e2e cluster tests (not our internal Jenkins config, but at least the test cases).

@hjacobs hjacobs self-assigned this Nov 2, 2016
@hjacobs hjacobs mentioned this issue Nov 2, 2016
femueller pushed a commit that referenced this issue Oct 5, 2018
* Fix empty strict_labels skipping all containers (#70)
* Additionally pass 'environment' label to Scalyr (#69)
* Fixes bug that strict labels are configured but not checked against (#67)
  * Fixes bug that strict labels are configured but not checked against
  * Updated test to verify if `strict_labels` are passed from down properly
  * Fixed formatting in test
* Adds configurable JSON log parsing(#49) (#66)
  * With the new configuration parameter `WATCHER_SCALYR_PARSE_LINES_JSON` the Scalyr agent can be configured to parse log lines as JSON entries which is useful to process raw Docker logs. This behaviour is disabled by default.

Signed-off-by: Felix Mueller <felix.mueller@zalando.de>
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

No branches or pull requests

1 participant