Deploy the release even if the last commit was skipped

TheQwertiest's Avatar


11 Sep, 2019 12:01 AM

Deployment scenario:
- Create a new tag on github in releases page.
- Appveyor build is triggered.
- Artifacts are pushed back to github after the build is finished.

If the last commit satisfies skipping criteria (e.g. `skip_commits` or [ci skip]), then the build is canceled and deployment never finishes.

Possible solution:
A new boolean field under `deploy`: `ignore_skip_rules`.

Example .yml with deployment setup:

  1. 1 Posted by Owen McDonnell on 12 Sep, 2019 02:07 PM

    Owen McDonnell's Avatar

    Can you elaborate this approach a little more (Problem: section of your post).
    Sorry, but for me it's a little hard to imagine too many users wanting to deploy a commit that they didn't want to build in the first place.

  2. 2 Posted by TheQwertiest on 12 Sep, 2019 07:29 PM

    TheQwertiest's Avatar

    It's quite simple. Here is an example:
    Commit history:
    - commit #0
    - commit #1
    - commit #2
    - commit #3 [skip ci]

    First release\deployment was on commit #0.
    Then we want to make the next release\deployment (latest commit is #3). This release will include commits #1 through #3. But because the latest commit is *skipped*, the whole deployment is canceled (despite having valid and needed commits).

  3. 3 Posted by Owen McDonnell on 13 Sep, 2019 04:46 AM

    Owen McDonnell's Avatar

    Ok, i've filed a feature request

  4. Feodor Fitsner closed this discussion on 03 Apr, 2020 06:44 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac