According to the instructions here:
https://confluence.atlassian.com/bitbucket/bitbucket-pipelines-faq-827104769.html
Adding [skip ci] to the last commit message should prevent a pipeline running.
However this doesn't work. Neither does [ci skip]
Part of my pipeline increments the version number and runs this
git add -Agit commit -m "version increment [skip ci]"git push origin master
But this triggers an infinite loop of builds. How can I stop this?
Hi @Ben Gannaway,
I was able to see the feature working fine with the following bitbucket-pipelines.yml script:
pipelines: default: - step: script: - echo test >> test.txt - git add -A - git commit -m "version increment [skip ci]" - git push origin master
Any change to a branch in my repository will trigger just one build and create a new commit with one more test on test.txt file.
Can you share more details on:
@Daniel Santos [skip ci] seems to be not working with pull request trigger.
Hi @Le Phuong
Can you confirm that the [skip ci] token is part of your merge commit for the pull request?
Yes it is.
As you can see in the support ticket you already submitted to our team, this is indeed a bug, more precisely this one [BCLOUD-17676] - Pull-request pipelines run with [skip ci].The branch builds will be skipped but the pull request build will still run, unfortunately.
I think that explains this behavior.
Any update regarding this ticket? I'm experiencing the same issue with the following config in my bitbucket-pipelines.yml
- yarn version --patch # Update patch version- echo "Made a change in build ${BITBUCKET_BUILD_NUMBER}"- git status- git push- git commit ./package.json -m "[skip CI] Patch version increment"- git push origin de
The CI proccess keeps re-triggering itself until my free minutes usage of pipelines run out.
Hi @Diego Marmol
The bug will affect a pipeline built for pull-request, but should not affect the ones running for the branch.
I see you are using
[skip CI]
instead of
[skip ci]
If this is not a pull request issue, it could be the way "skip ci" is written.
I've encountered to this problem since today. Is this a known problem? My automated skip ci commits keep triggering pipelines, using the following config.
image: node:ltsoptions:max-time: 5pipelines:pull-requests:feature/*: - step:name: Publishscript: - npm version prerelease -m "Upgrade to %s [skip ci]" - git push && git push --tags - pipe: atlassian/npm-publish:0.2.0variables:NPM_TOKEN: $NPM_TOKEN
afaik this is just basic pipelines configurations?
This is a screenshot of the pipelines overview page with the commit message containing [skip ci]
To all readers,
this problem is caused by a bug in pipelines. See this ticket for progress: https://jira.atlassian.com/browse/BCLOUD-17676
Yes, this bug was reported in different comment above, but the link redirect was affected due to a recent change in our issue system. Thank you for adding the new link here.
Do it yourself
- step script: - if [[ ! $(git log -1 --pretty=%B) =~ (\[ci skip\])|(\[skip ci\]) ]]; then git push; fi
and leave it.
That way even if it stops working in the future, you will have bulletproof piece of code.
Hi,
That's a nice idea. I tried it but it didn't work.
Maybe a free tier pipeline won't skip steps even with that script.
Hey everyone, not sure if this is still active but adding [skip ci] at the very beginning of the commit message seemed to have worked for me. I can confirm with both a straight push to master and from a pull request merge.
Doesn't appear to be working as of 2021-01-25
Same here the bug is still here and is not working
Adding to the start of a commit message when pushing on a commit to a branch worked for me.
It looks like you're new here. Sign in or register to get started.
