Use a dedicated cron runner #1

Closed
opened 2020-09-02 15:19:24 +02:00 by wanderer · 1 comment
Owner

Reason:
Drone cron builds recently have a tendency to hang in 'pending' state, which needs to get resolved manually every time it occurs, which is tedious.
Thus, I propose these options as a solution.

Options:

  • relatively flexible and transparent
    • outsource all DockeHub build triggers to a single own repo with it's own .drone.yml (and let it run on Drone cron which may or may not be even a greater issue than it already is, given all triggers could be impacted at once potentially)
  • not flexible and not transparent
    • crontab triggers
    • systemd-timer triggers
Reason: Drone `cron` builds recently have a tendency to hang in *'pending'* state, which needs to get resolved manually every time it occurs, which is tedious. Thus, I propose these options as a solution. Options: * relatively flexible and transparent * outsource all DockeHub build triggers to a single own repo with it's own .drone.yml (and let it run on Drone `cron` which may or may not be even a greater issue than it already is, given all triggers could be impacted at once potentially) * not flexible and not transparent * `crontab` triggers * `systemd-timer` triggers
wanderer added the Proposal label 2020-09-02 15:19:24 +02:00
wanderer self-assigned this 2020-09-02 15:19:24 +02:00
wanderer added a new dependency 2020-09-02 15:30:32 +02:00
wanderer added a new dependency 2020-09-02 15:36:12 +02:00
Author
Owner

this seemed to be a proxy (nginx) configuration issue, closing for now.
closes wanderer/docker-archlinux-hugo#1
closes wanderer/docker-fedora-hugo#1
closes wanderer/docker-alpine-rsync#1

this seemed to be a proxy (`nginx`) configuration issue, closing for now. closes wanderer/docker-archlinux-hugo#1 closes wanderer/docker-fedora-hugo#1 closes wanderer/docker-alpine-rsync#1
wanderer locked as Resolved and limited conversation to collaborators 2020-09-18 13:29:20 +02:00
Sign in to join this conversation.