Drone version: drone/drone:latest
Background
When promoting a tagged build with a commit containing [skip ci]
the promotion fails silently. Even though the original tag event was successfully completed.
Based on the Skipping | Drone docs, it seems ok to assume this should be triggered.
The skip directive is ignored for tags and promotion events, and when manually triggering pipelines.
In this case the first tag event was triggered where its promotion was ignored.
Expected behaviour
I would like to trigger a promotion via the UI or CLI and having the promotion starting its pipeline steps.
Actual behaviour
The promotion is never triggered and fails with the steps (4.1 and 4.2) listed below
Steps to reproduce:
- push a tag event with
v.2.0.1 [skip ci]
; - commit event is ignored (expected);
- tag event is triggered and completes successfully (expected)
[build 165]
; - Promote
[build 165]
tostable
environment channel;
4.1. UI silently fails with logUncaught (in promise) TypeError: n is null
- related #8716
4.2.drone build promote org/repo 165 stable
returns the bellow:
Number: 0
Status:
Event:
Commit:
Branch:
Ref:
Author:
Message: