如何在GitLab中实现推送或提交后自动触发流水线？

Hey there! I see you've got your GitLab pipeline up and running, but it's only triggering manually after code pushes or commits. Let's get that auto-trigger working smoothly—here's what you need to check and fix:

1. 确认项目CI/CD的自动触发设置 #

By default, GitLab CI automatically runs pipelines whenever you push code to any branch, tag, or create a merge request. If this isn't happening for you, start with your project's core settings:

• Navigate to your GitLab project → Settings (left sidebar) → CI/CD
• Scroll down to the General pipelines section
• Make sure the option like "Auto-run pipelines for new pushes" (wording might vary slightly by GitLab version) is enabled. Older versions might label this as "Enable pipelines for pushes"
• Also, check that there are no restrictive rules in the "Pipeline triggers" section blocking automatic runs for your target branches

2. 检查你的.gitlab-ci.yml配置 #

Looking at your provided config, I don't see any settings that would block auto-triggers—but let's confirm:

• Your config doesn't include only: [manual] or when: manual directives (which force manual triggering for jobs), so that's not the issue here
• There are no only/except rules restricting pipelines to specific branches/tags, which would prevent auto-runs on other branches

Here's your cleaned-up, properly formatted config for reference:

image: node:latest 

services:
  - mysql:latest 
  - redis:latest 
  - postgres:latest 

cache:
  paths:
    - node_modules/

test_async:
  script:
    - npm install
    - node ./specs/start.js ./specs/async.spec.js

test_db:
  script:
    - npm install
    - node ./specs/start.js ./specs/db-postgres.spec.js

3. 验证GitLab Runner状态 #

If pipelines still aren't auto-triggering, check if your assigned GitLab Runner is online and available:

• Go to your project → CI/CD → Runners
• Ensure the runner shows a green "Online" status. Offline runners will leave pipelines stuck in a pending state, making it seem like auto-triggers aren't working
• If you use tagged runners, confirm the runner has the tags matching any required by your pipeline jobs (your config doesn't use tags, so this shouldn't be a problem here)

4. 做一个简单的测试推送 #

After checking the above, make a tiny test commit (like updating a README line) and push it to your repo. Head to CI/CD → Pipelines in your project—you should see a new pipeline start automatically within a few seconds.

If you still hit snags, check the Pipeline history for error messages or pending states—those will usually give clues about why auto-triggers aren't kicking off.

内容的提问来源于stack exchange，提问作者Mansoor