CI integration reporting wrong URL on pending state #2199

Closed
opened 2025-11-02 04:26:49 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @Aragur on GitHub (Aug 14, 2018).

  • Gitea version (or commit ref): ca112f0
  • Git version: 2.18.0
  • Operating system: Debian
  • Database (use [x]):
    • MySQL
  • Can you reproduce the bug at https://try.gitea.io:
    • No (not possible)

Description

I am running a drone ci instance using the following docker-compose.yml

version: '2'

networks:
  drone:
    external: false
  proxy:
    external:
      name: proxy

services:
  drone-server:
    image: drone/drone:0.8
    expose:
      - 8000
      - 9000
    volumes:
      - ./drone:/var/lib/drone/
    restart: always
    networks:
      - proxy
      - drone
    environment:
      - DRONE_OPEN=true
      - DRONE_HOST={{REMOVED}}
      - DRONE_SECRET={{REMOVED}}
      - DRONE_GITEA=true
      - DRONE_GITEA_URL={{REMOVED}}
      - DRONE_GITEA_GIT_USERNAME=Drone
      - DRONE_GITEA_GIT_PASSWORD={{REMOVED}}
      - DRONE_GITEA_PRIVATE_MODE=true


  drone-agent:
    image: drone/agent:0.8

    command: agent
    restart: always
    networks:
      - drone
    depends_on:
      - drone-server
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - DRONE_SERVER=drone-server:9000
      - DRONE_SECRET={{REMOVED}}

After pushing into a activated repository Gitea shows the build status.
Example image
If the build succeeded the URL is working as expected (Redirecting to the defined DRONE_HOST)
But if a build is still pending or fails (this happens only 2 out of 10 if it fails, but everytime if it is pending) the URL redirects to http://drone-server:8000/

I don't think this is an intended behavior.
If you need any other details or configuration, let me know.

Originally created by @Aragur on GitHub (Aug 14, 2018). - Gitea version (or commit ref): ca112f0 - Git version: 2.18.0 - Operating system: Debian - Database (use `[x]`): - [x] MySQL - Can you reproduce the bug at https://try.gitea.io: - [x] No (not possible) ## Description I am running a drone ci instance using the following docker-compose.yml ``` version: '2' networks: drone: external: false proxy: external: name: proxy services: drone-server: image: drone/drone:0.8 expose: - 8000 - 9000 volumes: - ./drone:/var/lib/drone/ restart: always networks: - proxy - drone environment: - DRONE_OPEN=true - DRONE_HOST={{REMOVED}} - DRONE_SECRET={{REMOVED}} - DRONE_GITEA=true - DRONE_GITEA_URL={{REMOVED}} - DRONE_GITEA_GIT_USERNAME=Drone - DRONE_GITEA_GIT_PASSWORD={{REMOVED}} - DRONE_GITEA_PRIVATE_MODE=true drone-agent: image: drone/agent:0.8 command: agent restart: always networks: - drone depends_on: - drone-server volumes: - /var/run/docker.sock:/var/run/docker.sock environment: - DRONE_SERVER=drone-server:9000 - DRONE_SECRET={{REMOVED}} ``` After pushing into a activated repository Gitea shows the build status. ![Example image](https://user-images.githubusercontent.com/11004008/44058996-32bb097a-9f50-11e8-9d06-65a1e2cc26cb.png) If the build succeeded the URL is working as expected (Redirecting to the defined DRONE_HOST) But if a build is still pending or fails (this happens only 2 out of 10 if it fails, but everytime if it is pending) the URL redirects to http://drone-server:8000/ I don't think this is an intended behavior. If you need any other details or configuration, let me know.
GiteaMirror added the issue/stale label 2025-11-02 04:26:49 -06:00
Author
Owner

@lafriks commented on GitHub (Aug 15, 2018):

I think this should be reported to drone as Gitea can not know drone url, drone gives its own url to gitea

@lafriks commented on GitHub (Aug 15, 2018): I think this should be reported to drone as Gitea can not know drone url, drone gives its own url to gitea
Author
Owner

@Aragur commented on GitHub (Aug 15, 2018):

I already reported it, but the issue got instantly closed: https://github.com/drone/drone/issues/2470

@Aragur commented on GitHub (Aug 15, 2018): I already reported it, but the issue got instantly closed: https://github.com/drone/drone/issues/2470
Author
Owner

@stale[bot] commented on GitHub (Jan 13, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 13, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Feb 20, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 20, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2199