GitLab Environment — CI/CD for FiveM

Use GitLab CI/CD to build and deploy FiveM resources from your private group to your game server.

Overview

Your GitLab Environment includes pipeline templates oriented toward game server workflows:

1. Push code to your repository
2. Pipeline runs on GitLab runners tagged for your infrastructure
3. Artifacts or deploy scripts copy resources to the target server

Exact pipeline YAML depends on your server layout — check the .gitlab-ci.yml in your group template or starter project.

Typical setup

1. Repository — store resources/, configs, or packaged assets in Git
2. Variables — add deploy host, SSH key, or API tokens under Settings → CI/CD → Variables
3. Runner tags — pipelines use runners available to your GitLab instance (contact support if jobs stay pending with no runner)
4. Deploy job — rsync, SCP, or custom script to /opt/fivem/... or your server path

Example pattern (conceptual)

deploy:
  stage: deploy
  script:
    - rsync -avz ./resources/ user@your-server:/path/to/resources/
  only:
    - main

Adapt paths and authentication to your environment. Use protected branches so only main deploys to production.

FiveM-specific tips

• Restart only the resources that changed when possible (ensure / refresh in txAdmin or your workflow)
• Keep server.cfg changes in Git or document them separately
• Pair with CFX File Cache — after deploy, purge edge cache if players see stale files (see CFX File Cache docs)
• Store Kuzzle and CDN URLs in CI variables, not in committed secrets

Pipeline failures

• Runner not available — job stuck pending; verify runner tags match .gitlab-ci.yml
• SSH failed — check deploy key variable and server firewall (port 22)
• Permission denied — target path ownership on the game server

Open a support ticket with pipeline job logs if you need help with Nexus-provided runner configuration.