Gitlab CI job fails after commit but successful when manual

GitLab CI/CD
1

Gitlab CI job fails after commit but successful when manual

Describe your question in as much detail as possible:

  • I have a CI job that builds static written on npm. When I commit the pipeline triggers and the job starts.

  • The problem is that it fails sometimes and sometimes not. The interesting fact is that it fails in different places. The failure does not depend on language as I guess.

  • Another thing is that when I trigger pipeline manually (using run pipeline button), it always success, I have not seen any problem. It fails only when commit.

    • GitLab (Hint: /help): 14.1.0
    • Runner (Hint: /admin/runners): 14.1.0

  • I have not found any information about that problem. I tried to monitor CPU load during job running but did not notice any difference between running after commit and after manual trigger*

Maybe someone have faced such problem and have any idea how to fix it. Thanks in advance!

2

@RockstarAlex Welcome to the forum and thanks for the post!

Could you include a snippet of your .gitlab-ci.yml it could be some rules or only keywords that are preventing some commits from triggering the pipeline.

-James H, GitLab Product Manager, Verify:Pipeline Execution