I have a pipeline that runs quite a lot of supporting services for various test scenarios executed by gradle. Because of gradle I don’t want to move them to independent steps, but this means that 2 of these supporting services are the same thing, with slightly different configuration. The problem is obviously that the service port is identical in this case, and I can’t figure out if port forwarding is functional in services. I can hit them over the default service port, but the forwarding rules used in compose fail to unmarshall in yaml and without the mapping
it doesn’t do anything.
Is this meant to be functional / is there an alternative to this?
--- kind: pipeline type: kubernetes name: smoke-artefact-layers platform: os: linux arch: amd64 environment: registry: xy workspace: path: /drone/src depends_on: - linting services: - name: dind-engine image: docker:dind privileged: true commands: - dockerd --host=tcp://0.0.0.0:2375 - name: minio1 image: minio/minio commands: - minio server /data environment: MINIO_ACCESS_KEY: secret1 MINIO_SECRET_KEY: secret2 ports: - 9001 expose: - 9000 - name: minio2 image: minio/minio commands: - minio server /data environment: MINIO_ACCESS_KEY: secret3 MINIO_SECRET_KEY: secret4 ports: - 9002 expose: - 9000 steps: - name: build image: docker:dind privileged: true environment: DOCKER_HOST: tcp://dind-engine:2375 commands: - | tests in gradle commands to connect to minio1 and minio2 trigger: branch: - master event: - pull_request - push