"skip ci" in commit message not working

[BoazWarshawsky]

I am trying to find a way to skip Azure CI via the commit message, when trying the following messages none of them really do the work and skip the CI run:
[skip ci] or [ci skip]
skip-checks: true or skip-checks:true
[skip azurepipelines] or [azurepipelines skip]
[skip azpipelines] or [azpipelines skip]
[skip azp] or [azp skip]
NO_CI

[DotNetSparky]

For on-prem server, try this: ***NO_CI***
(include the asterisks)

The others might only work for Azure DevOps Services (the hosted version), they don't show up in the docs when I switch the filter to "Azure DevOps Server 2019" (https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops-2019)

[petong]

I am having the same issue, and from what I have read in #858 placing [skip ci] in a commit message only skips on merge to master and not in a PR run, which is totally bizarro!

[BoazWarshawsky]

***NO_CI*** is not working too

[jeliasson]

Until we have a proper fix in place, here is a temporary fix that will skip the script execution if the commit message (Build.SourceVersionMessage) contains skip ci. Using a variable if the condition is repeated for more scripts.

variables:
    SKIP_CI_FILTER: 'skip ci'

steps:
  - script: sh ./script1.sh
    condition: not(contains(variables['Build.SourceVersionMessage'], variables['SKIP_CI_FILTER']))

[jtpetty]

@vtbassmatt - Do you have any context here? Is this our recommended solution?

[vtbassmatt]

I believe we honor SKIP_CI and friends only when the commit containing that value is the tip, whether it's CI or PR. If you merge using GitHub's PR experience, for example, I don't think the SKIP_CI indicator gets included in the merge commit unless you included it in the PR message body.

[artemry-nv]

@vtbassmatt
Are there any plans to add a possibility to skip PR triggering with [skip ci] comments?

[vtbassmatt]

I believe that should also work (as long as the [skip ci] is in the head commit of the push).

[ihnorton]

@vtbassmatt it does not work. See this build, the head commit of which is TileDB-Inc/TileDB-Py@68d937f.

[vtbassmatt]

Hmm, that sounds like a bug in the service then. Could you please file a report on Developer Community?

I'm going to close this issue because the bug can't be in the agent. (The agent just runs what the service tells it to run.)

[ihnorton]

https://developercommunity.visualstudio.com/content/problem/714477/pr-commit-with-skip-ci-in-message-still-triggers-a.html

[vtbassmatt]

That issue has been routed to a developer to investigate. Thanks for your patience.

[Vic152]

Is this being fixed?

[alvindutt]

Hi All

Is this still an issue on PR triggers?

[PaulTaykalo]

This is not about commit-based, but rather PR based, still

# Variable that checks if the PR title contains '[skip ci]' or '[skip build]'
variables:
  - name: should_skip_ci
    value: |
      or(contains(variables['System.PullRequest.PullRequestTitle'], '[skip ci]'), contains(variables['System.PullRequest.PullRequestTitle'], '[skip build]'))

stages:

  # Stage for checking if CI should be skipped
  # Then we can skip the rest of the CI pipeline by adding dependsOn: check_skip_ci 
  - stage: check_skip_ci
    displayName: Check if CI should be skipped
    condition: not(variables['should_skip_ci'])
    jobs:
      - job: check_skip_ci
        displayName: Check if CI should be skipped
        steps:
          - script: echo "This is a dummy job to check if CI should be skipped. Since Azure doesnt allow empty stages without jobs"

  - stage: build
    dependsOn: check_skip_ci

  ## OR
  - stage: build
    condition: and(succeeded(), not(variables['should_skip_ci']))