netty5/docker/docker-compose.centos-6.18.yaml

version: "3"

services:

  runtime-setup:
    image: netty:centos-6-1.8
    build:
      args:
        java_version : "adopt@1.8.0-272"

  build:
    image: netty:centos-6-1.8

  build-leak:
    image: netty:centos-6-1.8

  build-boringssl-static:
    image: netty:centos-6-1.8

  build-leak-boringssl-static:
    image: netty:centos-6-1.8

  stage-snapshot:
    image: netty:centos-6-1.8

  deploy:
    image: netty:centos-6-1.8

  shell:
    image: netty:centos-6-1.8
add docker-compose to allow easy testing across linux and java versions (#7958) motivation: setup for testing across different permutations of linux and java versions changes: * refactor docker file to allow dynamic versions of centos and java * add docker compose driver files for centos 6, 7 and java 1.8, 1.9, 1.10, 1.11 * update instructions 2018-05-28 10:31:48 +02:00			`version: "3"`

			`services:`

			`runtime-setup:`
			`image: netty:centos-6-1.8`
			`build:`
			`args:`
Update to latest java 8/11/15 versions (#10774) Motivation: There were new releases of java. Modifications: Update java versions so we use the latest on the CI Result: Use latest releases 2020-11-04 10:39:55 +01:00			`java_version : "adopt@1.8.0-272"`
add docker-compose to allow easy testing across linux and java versions (#7958) motivation: setup for testing across different permutations of linux and java versions changes: * refactor docker file to allow dynamic versions of centos and java * add docker compose driver files for centos 6, 7 and java 1.8, 1.9, 1.10, 1.11 * update instructions 2018-05-28 10:31:48 +02:00
Use Github workflows for CI (#10879) Motivation: We should just use GitHub Actions for the CI Modifications: - Adjust docker / docker compose files - Add different workflows and jobs to deploy and build the project Result: Don't depend on external CI services 2020-12-22 18:33:14 +01:00			`build:`
			`image: netty:centos-6-1.8`

			`build-leak:`
			`image: netty:centos-6-1.8`

Also include one PR job that uses boringssl (#10886) Motivation: When validating PRs we should also at least run one job that uses boringssl Modifications: - Add job that uses boringssl - Cleanup docker compose files - Fix buffer leak in test Result: Also run with boringssl when PRs are validated 2020-12-23 19:11:04 +01:00			`build-boringssl-static:`
add docker-compose to allow easy testing across linux and java versions (#7958) motivation: setup for testing across different permutations of linux and java versions changes: * refactor docker file to allow dynamic versions of centos and java * add docker compose driver files for centos 6, 7 and java 1.8, 1.9, 1.10, 1.11 * update instructions 2018-05-28 10:31:48 +02:00			`image: netty:centos-6-1.8`
Allow to test with boringssl-static and drop into shell (#7980) Motivation: We also need to run our tests while using boringssl-static to ensure everything works when using it. Beside this its sometimes useful to be able to just get a shell and so interactive work in the docker instance. Modifications: - Add configs for shell - Add configs for testing with boringssl-static - Ensure we not share .m2 when running tests Result: More complete docker setup. 2018-05-29 11:09:22 +02:00
Also include one PR job that uses boringssl (#10886) Motivation: When validating PRs we should also at least run one job that uses boringssl Modifications: - Add job that uses boringssl - Cleanup docker compose files - Fix buffer leak in test Result: Also run with boringssl when PRs are validated 2020-12-23 19:11:04 +01:00			`build-leak-boringssl-static:`
Allow to run tests with leak detection enabled. (#8323) Motivation: We should add some command to be able to run all tests with leak detection enabled. This will then be used on the CI during PR builds. Modifications: Add new docker-compose config to run with leak-detection enabled. Result: Easy way to enable leak detection while running tests via docker. 2018-09-27 09:13:28 +02:00			`image: netty:centos-6-1.8`

Correctly deploy artifacts that are build on different archs (#10893) Motivation: We need to take special care when deploying snapshots as we need to generate the jars in multiple steps Modifications: - Use the nexus staging pluging to stage jars locally in multiple steps - Add extra job that will merge these staged jars and deploy these Result: Fixes https://github.com/netty/netty/issues/10887 2020-12-24 12:00:08 +01:00			`stage-snapshot:`
			`image: netty:centos-6-1.8`

Also include one PR job that uses boringssl (#10886) Motivation: When validating PRs we should also at least run one job that uses boringssl Modifications: - Add job that uses boringssl - Cleanup docker compose files - Fix buffer leak in test Result: Also run with boringssl when PRs are validated 2020-12-23 19:11:04 +01:00			`deploy:`
Allow to test with boringssl-static and drop into shell (#7980) Motivation: We also need to run our tests while using boringssl-static to ensure everything works when using it. Beside this its sometimes useful to be able to just get a shell and so interactive work in the docker instance. Modifications: - Add configs for shell - Add configs for testing with boringssl-static - Ensure we not share .m2 when running tests Result: More complete docker setup. 2018-05-29 11:09:22 +02:00			`image: netty:centos-6-1.8`

			`shell:`
			`image: netty:centos-6-1.8`