How connect to my own pipeline service ( not other concurrent running from other pipelines)?

Hello to everybody in this forum and for all moderators that are doing a great work.

I have a question about concurrent pipelines and services defined over them… when I’ve configured my drone-runner (over docker swarm) to attach all created containers on the same net “mynet-public” , because of needed to access external services.

  drone-runner:
    image: drone/drone-runner-docker:latest
    networks:
      - mynet-public
    environment:
      DRONE_RPC_HOST: drone-server
      DRONE_RPC_PROTO: http
      DRONE_RPC_SECRET: ${WEB_MYNET_ADMIN_PASSWORD}
      DRONE_RUNNER_CAPACTIY: 8
      DRONE_DEBUG: "true"
      DRONE_TRACE: "true"
      DRONE_LOGS_TRACE: "true"
      DRONE_RUNNER_ENVIRON:  GIT_SSL_NO_VERIFY:"true"
      DRONE_RUNNER_NETWORKS: mynet-public
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    deploy:
      mode: global
      placement:
        constraints:
          - node.labels.mynet-role.drone-runner  == true

I would like to design a unique pipeline for a lot of different repos, something like that.

kind: pipeline
type: docker
name: default

steps:
  - name: get_info
    image: alpine
    commands:
    - curl http:///my-web-server/?query=info

services:
  - name: my-web-server
    image: images/my-web-server-image

If repoA triggers PIPELINE-A I need the “get_info” step on the PIPELINE-A could connect to “my-web-server” service on the PIPELINE-A with data from the repoA.

What happens if at the same time repoB triggers PIPELINE-B and get_info step try to connect with my-web-server service ? Could connect with “my-web-server” service from PIPELINE-A with data from repoA instead of data from repoB ?

Thank you in advance!

Hi @everybody.

I did the following test , And I solved myself my question.

I’ve created two repos,

test_web_client_repo

kind: pipeline
type: docker
name: robot_test1_ie_win


steps:
- name: test_content12
  image: alpine
  commands:
    - sleep 30
    - ping -c 1 test_service_webX 
    - nc -vz test_service_webX 8080
    - wget http://test_service_webX:8080
    - cat index.html
    - grep WEB1 index.html

test_web_server_repo

kind: pipeline
type: docker
name: robot_test1_ie_win


services:
- name: test_service_webX
  image: my_dummy_web_server
  ports:
   - 8080

steps:
- name: forced_sleep
  image: alpine
  commands:
    - sleep 36000

I’ve forced pipeline from “test_web_server_repo” to be working for a while with a dummy webserver service serving at " test_service_webX" and after that i’ve forced “test_web_client_repo” to start pipeline, with this result

pipeline from “test_web_client_repo” can not resolve service name from “test_web_server_repo” , even with the same network “mynet-public” attached to both pipelines.

It works ok to me !!!

Thank you to everybody who is working in this project again!!