Skip CI requests

[jakirkham]

Trying to keep track of these in one place.

1. Make [ci skip] work in PRs for CircleCI. ( ref )
2. Have [circle skip] to skip CircleCI specifically. ( ref )
3. Have [travis skip] to skip Travis CI specifically. ( Add a [skip travis] command travis-ci/travis-ci#5032 )

[jakirkham]

Appears CircleCI now respects [ci skip] on pull requests, but not [skip ci] yet.

[smithsp]

What is the placement of these strings? In a commit message, or in a pull request title? What about [skip appveyor]?

[CJ-Wright]

In the commit message.

[CJ-Wright]

I don't know if appveyor has a skip. @jakirkham does appveyor have a skip?

[smithsp]

https://github.com/conda-forge/staged-recipes/#3-how-do-i-exclude-a-platform

[CJ-Wright]

Not the same, that skips the CI forever. We just want to skip the CI temporally. (eg the only change you made was removing a comment). The CIs will all run as proper when we go to merge (or one puts in another commit without those in the message)
Edit: I take that all back, it seems that there is an appveyor skip, sorry (I was looking at the wrong section)

[CJ-Wright]

Just for ease of reference [skip appveyor] is listed in the Readme as @smithsp found.

[smithsp]

It is odd that I added those strings in my commit message, but #4540 still triggered circleci and appveyor builds.

[CJ-Wright]

It seems they can be a bit fickle.

[jakirkham]

Probably should add that the ones listed in the OP are all ones that don’t work, but we or others have requested the CIs add them.

[smithsp]

Note that I found https://www.appveyor.com/docs/how-to/filtering-commits/ which indicates the [skip appveyor] (or [skip ci]) directive must be in the git commit title line for appveyor. My latest commit in #4560 seems to confirm this.

[jakirkham]

That's correct. Also issue ( appveyor/ci#1865 ) may be of interest w.r.t. AppVeyor's commit filtering.

[croth1]

Does anybody have an overview of the current status?

• travis, appveyor: it looks like travis and appveyor have implemented specific skips.
• circle: was an update last month: https://discuss.circleci.com/t/adding-circle-skip-to-commit-message-to-skip/2778/19, but I don't know the progress
• azure: I have no data

I think it would be interesting to collect all of these in the documentation: http://conda-forge.org/docs/maintainer/infrastructure.html#skipping-ci-builds

It would be also interesting to have instructions to skip mac and windows but not linux, etc.

[ceholden]

Just came across an update for Azure on their issue tracker (post) -- they've just enabled skipping for commit messages with [skip ci] and a few other tags

[EDIT]: Doesn't look like it's working yet! https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=25184

[kynan]

Is there any update on this? The docs mention [ci skip] ***NO_CI*** as the tag to include, but that doesn't seem to have any effect for Azure.

Can I still safely push a commit without triggering a new build and new packages to be published?

[kynan]

Ideally, I'd like the linter to still run on my recipe, but be sure that no builds will be triggered.

[beckermr]

It doesn't work for azure pull requests but it does work on the master branch of the feedstock.

[kynan]

OK. Just to make sure I understand correctly: when I want to skip CI I should be committing directly commit to master and not make a PR?

[beckermr]

Nope. Still use prs. It is just that ci skip in prs may not work. However prs do not upload packages so this isn't an issue.