2.0 job
#2329 is triggered via push, skip is correct
#2330 is triggered via API, build running
#2331 is triggered via API, skipped due to [skip ci] ??
#2332 is triggered via API, build running
#2333 is triggered via API, skipped due to [skip ci] ??
Is this a BUG?
6 months later, bug is still here.
Yes, that does not look right. What would you regard as correct behaviour here? I wonder if calling the API should always run or always skip?
Yes, if I commited a [skip ci] I meant to skip the build after the push, not to skip (half) build invoked via API for the same commit.
However I think the bug also involves timing, because if I wait a few minutes before triggering another build via API it didn’t get skipped.
FYI, I also opened a support ticket a few minutes ago referencing this thread.
Thanks.
Another closed bug report with the same issue: Build triggered from API cancelled if last commit contains [skip ci] with no response.
API triggers should not be associated with git triggers! This one is frustrating! I keep running into issues with circleci and triggering child builds.
Did you hear anything back @gionn ?
I’ve opened a support ticket and they acknowledged a bug on their side, still waiting for the fix.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
