GitLab CI

Overview

FixSense supports GitLab CI alongside GitHub Actions. When a Playwright or Cypress pipeline fails on GitLab, FixSense automatically downloads artifacts, parses test results, and delivers AI-powered root cause analysis — just like it does for GitHub.

Requirements

• A GitLab project with Playwright or Cypress tests
• A GitLab Project Access Token with api scope (Maintainer role or higher)
• Test framework configured with a JSON reporter:

// playwright.config.ts
export default defineConfig({
  reporter: [
    ['html'],
    ['json', { outputFile: 'test-results/report.json' }],
  ],
});

• CI artifacts configured to include test-results/:

# .gitlab-ci.yml
playwright-tests:
  image: mcr.microsoft.com/playwright:v1.58.2-noble
  script:
    - npm install
    - npx playwright test
  artifacts:
    when: always
    paths:
      - test-results/
    expire_in: 7 days

Setup

Step 1: Sign in with GitLab

Go to the FixSense login page and click Sign in with GitLab. This grants FixSense read access to your GitLab profile and projects.

Step 2: Connect your project

1. Open the Setup page
2. Enter your GitLab project path (e.g. my-group/my-project)
3. Enter a Project Access Token with api scope
4. Click Connect

FixSense will automatically:

• Verify the token has access to the project
• Register a webhook on the project for pipeline and merge request events
• Save the configuration

Step 3: Trigger a pipeline

Push a commit or run a pipeline manually. When a test fails, FixSense will:

1. Receive the pipeline webhook
2. Download test artifacts from the failed job
3. Parse the test JSON report (Playwright or Mochawesome)
4. Run AI analysis on each failure
5. Post results to the dashboard (and optionally as MR comments)

Features

All core FixSense features work with GitLab:

GitLab vs GitHub Differences

Troubleshooting

"Cannot create webhook" error during setup

Your Project Access Token needs Maintainer role or higher on the project. Alternatively, ask a project admin to manually add the webhook:

• URL: https://fix-sense.com/api/webhooks/gitlab
• Secret token: (provided during setup)
• Triggers: Pipeline events, Merge request events

No analyses appear after pipeline failure

1. Check that your .gitlab-ci.yml uploads test-results/ as artifacts
2. Verify your test framework config includes a JSON reporter (Playwright: outputFile: 'test-results/report.json', Cypress: Mochawesome reporter)
3. Check that the pipeline webhook was delivered (GitLab > Settings > Webhooks > Recent events)

Artifacts are empty or too small

Make sure artifacts are set to when: always so they're uploaded even when the job fails.