andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
37c03cce5e
netty5/docker/docker-compose.yaml

68 lines
2.2 KiB
YAML
Raw Normal View History

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:default
build:
context: .
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
dockerfile: Dockerfile.centos6
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
common: &common
image: netty:default
depends_on: [runtime-setup]
Use MAVEN_OPTS to setup timeouts for dependency downloads (#11250) Motivation: Just use MAVEN_OPTS to setup all the timeouts etc for dependency downloads. This way we at least can be sure these are applied. Modifications: - Use MAVEN_OPTS - Remove ci profile - Remove unused settings.xml file - Always use ./mvnw Result: Build stability improvements
2021-05-12 18:02:35 +02:00
environment:
- GPG_KEYNAME
- GPG_PASSPHRASE
- GPG_PRIVATE_KEY
- MAVEN_OPTS
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
volumes:
Add deploy job for cross compiled aarch64 (#10883) Motivation: We should also deploy snapshots for our cross compiled native jars. Modifications: - Add job and docker files for deploying cross compiled native jars - Ensure we map the maven cache into our docker containers Result: Deploy aarch64 jars and re-use cache
2020-12-22 20:43:35 +01:00
- ~/.ssh:/root/.ssh
- ~/.gnupg:/root/.gnupg
- ~/.m2:/root/.m2
- ..:/code
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
working_dir: /code
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-leak:
<<: *common
Make build log output less chatty (#11365) Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: Make all Maven builds run in batch mode by adding the `-B` command line flag, and have transfer progress suppressed with the `-ntp` flag. Some builds were already running batch mode but had the flag in a different location – these have had their `-B` flag moved so all builds are consistent. Result: Much less output in our build logs where Maven is just downloading stuff.
2021-06-07 10:53:10 +02:00
command: /bin/bash -cl "./mvnw -B -ntp -Pleak clean install -Dio.netty.testsuite.badHost=netty.io -Dtcnative.classifier=linux-x86_64-fedora"
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:
<<: *common
Make build log output less chatty (#11365) Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: Make all Maven builds run in batch mode by adding the `-B` command line flag, and have transfer progress suppressed with the `-ntp` flag. Some builds were already running batch mode but had the flag in a different location – these have had their `-B` flag moved so all builds are consistent. Result: Much less output in our build logs where Maven is just downloading stuff.
2021-06-07 10:53:10 +02:00
command: /bin/bash -cl "./mvnw -B -ntp clean install -Dio.netty.testsuite.badHost=netty.io -Dtcnative.classifier=linux-x86_64-fedora"
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
Fix deploy config
2020-12-22 18:48:22 +01:00
deploy:
<<: *common
Make build log output less chatty (#11365) Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: Make all Maven builds run in batch mode by adding the `-B` command line flag, and have transfer progress suppressed with the `-ntp` flag. Some builds were already running batch mode but had the flag in a different location – these have had their `-B` flag moved so all builds are consistent. Result: Much less output in our build logs where Maven is just downloading stuff.
2021-06-07 10:53:10 +02:00
command: /bin/bash -cl "./mvnw -B -ntp clean deploy -DskipTests=true"
Fix deploy config
2020-12-22 18:48:22 +01:00
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:
<<: *common
volumes:
- ~/.ssh:/root/.ssh
- ~/.gnupg:/root/.gnupg
- ~/.m2:/root/.m2
- ~/local-staging:/root/local-staging
- ..:/code
Make build log output less chatty (#11365) Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: Make all Maven builds run in batch mode by adding the `-B` command line flag, and have transfer progress suppressed with the `-ntp` flag. Some builds were already running batch mode but had the flag in a different location – these have had their `-B` flag moved so all builds are consistent. Result: Much less output in our build logs where Maven is just downloading stuff.
2021-06-07 10:53:10 +02:00
command: /bin/bash -cl "./mvnw -B -ntp clean package org.sonatype.plugins:nexus-staging-maven-plugin:deploy -DaltStagingDirectory=/root/local-staging -DskipRemoteStaging=true -DskipTests=true"
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
Add workflow to cut releases (#11019) Motivation: Doing releases manually is error-prone, it would be better if we could do it via a workflow Modification: - Add workflow to cut releases - Add related scripts Result: Be able to easily cut a release via a workflow
2021-02-11 21:35:36 +01:00
stage-release:
<<: *common
volumes:
- ~/.ssh:/root/.ssh
- ~/.m2:/root/.m2
- ~/local-staging:/root/local-staging
- ..:/code
Make build log output less chatty (#11365) Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: Make all Maven builds run in batch mode by adding the `-B` command line flag, and have transfer progress suppressed with the `-ntp` flag. Some builds were already running batch mode but had the flag in a different location – these have had their `-B` flag moved so all builds are consistent. Result: Much less output in our build logs where Maven is just downloading stuff.
2021-06-07 10:53:10 +02:00
command: /bin/bash -cl "cat <(echo -e \"${GPG_PRIVATE_KEY}\") | gpg --batch --import && ./mvnw -B -ntp clean javadoc:jar package gpg:sign org.sonatype.plugins:nexus-staging-maven-plugin:deploy -DnexusUrl=https://oss.sonatype.org -DserverId=sonatype-nexus-staging -DaltStagingDirectory=/root/local-staging -DskipRemoteStaging=true -DskipTests=true -Dgpg.passphrase=${GPG_PASSPHRASE} -Dgpg.keyname=${GPG_KEYNAME} -Dtcnative.classifier=linux-x86_64-fedora"
Add workflow to cut releases (#11019) Motivation: Doing releases manually is error-prone, it would be better if we could do it via a workflow Modification: - Add workflow to cut releases - Add related scripts Result: Be able to easily cut a release via a workflow
2021-02-11 21:35:36 +01: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-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
<<: *common
Make build log output less chatty (#11365) Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: Make all Maven builds run in batch mode by adding the `-B` command line flag, and have transfer progress suppressed with the `-ntp` flag. Some builds were already running batch mode but had the flag in a different location – these have had their `-B` flag moved so all builds are consistent. Result: Much less output in our build logs where Maven is just downloading stuff.
2021-06-07 10:53:10 +02:00
command: /bin/bash -cl "./mvnw -B -ntp -Pboringssl clean install -Dio.netty.testsuite.badHost=netty.io -Dxml.skip=true"
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
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:
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
<<: *common
Make build log output less chatty (#11365) Motivation: When Maven does not run in batch mode, it will continuously print its progress as it downloads dependencies. This can produce a very large amount of log output, that makes it harder to debug build failures. Modification: Make all Maven builds run in batch mode by adding the `-B` command line flag, and have transfer progress suppressed with the `-ntp` flag. Some builds were already running batch mode but had the flag in a different location – these have had their `-B` flag moved so all builds are consistent. Result: Much less output in our build logs where Maven is just downloading stuff.
2021-06-07 10:53:10 +02:00
command: /bin/bash -cl "./mvnw -B -ntp -Pboringssl,leak clean install -Dio.netty.testsuite.badHost=netty.io -Dxml.skip=true"
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
shell:
<<: *common
Use aarch_64 in a consistent way (#10845) Motivation: We should use aarch_64 in our classifier / jni libname on aarch64 as os.detected.arch uses the name. Being non consistent (especially across our different projects) already gave us a lot of trouble in the past. Let's fix this once for all. Modifications: Use aarch_64 Result: More consistent classifier usage on aarch64
2020-12-07 12:14:23 +01:00
entrypoint: /bin/bash
Reference in New Issue Copy Permalink