Build badge showing as "error"

Unsure why this is happening, doesn’t happen for all builds in this particular case.

# Drone Server
  drone:
    container_name: DroneCI
    image: drone/drone
    restart: always
    volumes:
      - $USERDIR/Drone:/data
      - /var/run/docker.sock:/var/run/docker.sock
    networks:
      pihole:
        ipv4_address: '172.22.0.129'
    ports:
      - "1080:80"
    environment:
      - DRONE_GITHUB_SERVER=https://github.com
      - DRONE_GITHUB_CLIENT_ID=${DRONE_GITHUB_CLIENT_ID}
      - DRONE_GITHUB_CLIENT_SECRET=${DRONE_GITHUB_CLIENT_SECRET}
      - DRONE_GIT_ALWAYS_AUTH=false
      - DRONE_RUNNER_CAPACITY=2
      - DRONE_SERVER_HOST=drone.${DOMAINNAME}
      - DRONE_USER_CREATE=username:$DRONE_USER,admin:true
      - DRONE_SERVER_PROTO=https
      - DRONE_LOGS_DEBUG=true
      - DRONE_LOGS_TEXT=true
      - DRONE_LOGS_PRETTY=true
      - DRONE_LOGS_COLOR=true
      - DRONE_RPC_SECRET=$DRONE_RPC_SECRET
      - DRONE_USER_FILTER=$DRONE_USER

Live example: Docker

Builds are working as expected: https://drone.modem7.com/modem7/guacamole/14

Typical - as soon as I post, it starts working.

Consider this closed!

The code path for displaying an error badge is if the last build (ie. last master build) had an error status. An error status could be caused by an invalid yaml, for example. So in this case an error badge is valid state.

The code for the badge handler is relatively short, if you are interested in learning more:

1 Like