[TeamCity, FAILED] Build netty-tcnative :: build [master] #310

[team...@netty.io]

Build netty-tcnative :: build [master] #310 failed (Exit code 1 (new))

Agent: debian8-2

Changes included: 4 changes.

Change 9406285cbd942938a91239293dfb87fe0def4146 by norman_maurer (5 files): [maven-release-plugin] prepare for next development iteration

Change cb6db72c7e6ad729b140783265b6a45b0caf4505 by norman_maurer (5 files): [maven-release-plugin] prepare release netty-tcnative-parent-2.0.19.Final

Change a6c62f77eb2892d503d87ceaaa48279dc92ed550 by norman_maurer (2 files): Explicit specify java version to use to ensure we rebuild image when java version changes. (#408)

Motivation:

We should explicit specify the java version to use to ensure docker will rebuild the image once a new java version was released and we specify it.

Modifications:

- Explicit specify the java versions to use

Result:

Ensure latest java versions are used during testing

Change 631fc75c89aca01b4850f7117a5137cc4181a143 by norman_maurer (2 files): Cleanup BoringSSL TLSv1.3 support and consistent handle empty ciphers. (#407)

Motivation:

Some code can be removed and also we should ensure we handle empty ciphers consistent between BoringSSL and OpenSSL.

Modifications:

- Remove not needed called for min protocol version when using BoringSSL
- Return when an empty ciphers string is given as this will fail in BoringSSL while just return on OpenSSL.

Result:

Cleaner and more consistent code.

Configure your email notifications on your settings page.