1.0.0-rc.1: Building my first pipeline: builds never start

Drone Support
1

Hello,

I’ve updated the helm/charts/stable/drone chart to support drone-1.0.0. I am able to access the drone server, via an https ingress. I am also able to add a github repository, the webhook is created, and github reports the payload was delivered. When I look at my drone repository’s activity feed, I see the pipeline job, I click the “play” button, to follow the logs, but there are no logs. There is no activity. I turned on debugging (DRONE_DEBUG: true), no extra information is printed.

Does anyone see what I might be missing?

server logs

$ kubectl -n drone logs drone-drone-server-7457fc7656-q5b75
{"interval":1800000000000,"level":"info","msg":"main: cron schedule disabled","time":"2018-11-27T16:38:52Z"}
{"acme":false,"host":"drone","level":"info","msg":"main: starting the http server","port":":80","proto":"https","time":"2018-11-27T16:38:52Z","url":"https://drone"}
{"level":"info","msg":"main: local build runner disabled","time":"2018-11-27T16:38:52Z"}

agent logs

$ kubectl -n drone logs drone-drone-agent-bdc7f6c6f-pc5xh drone-drone-agent
{"level":"info","msg":"starting the build runner","server":"drone-drone","threads":1,"time":"2018-11-27T16:38:48Z"}

drone yaml

$ cat .drone.yml
kind: pipeline
name: default
steps:
  - name: test
    image: clojure
    pull: always
    commands:
      - ./scripts/test.sh
    environment:
      POSTGRES_PORT_5432_TCP_ADDR: postgres
      POSTGRES_PORT_5432_TCP_PORT: 5432
      REDIS_PORT_6379_TCP_ADDR: redis
      REDIS_PORT_6379_TCP_PORT: 6379


services:
  - name: redis
    image: redis:3
  - name: postgres
    image: postgres:9.6-alpine
2

I turned on debugging ( DRONE_DEBUG: true ), no extra information is printed.

You need to use DRONE_LOGS_DEBUG for debug logging.

I see the pipeline job, I click the “play” button, to follow the logs, but there are no logs. There is no activity.

This would imply that the build did not start, likely because the agent was unable to connect to the server and process a build. I recommend temporarily adding DRONE_RPC_DEBUG=true to your agent which will print more verbose http connection details.

I would also recommend double-checking your configuration based on the updated install docs. The configuration changed significantly and we’ve seen issues where individuals use 0.8 configuration parameters or settings with 1.0, leading to an invalid configuration.

3

Thanks so much for the quick reply! It turned out that did not include the scheme, for the RPC server url. I believe that with this update I should be able to open a pr for the chart! I know v1 is an RC right now… Do you think I should wait until you do a final release, or do you anticipate the environment variables will stay as they are?

edit: perhaps more importantly, is there a list of env vars for v1 any where?

4

I believe that with this update I should be able to open a pr for the chart! I know v1 is an RC right now… Do you think I should wait until you do a final release, or do you anticipate the environment variables will stay as they are?

I recommend waiting until the final release, since some of the parameters are in flux.

perhaps more importantly, is there a list of env vars for v1 any where?

Yes, you can find a full list of parameters here

5

Excellent. Looking forward to v1! Thanks for your work.