Skip to content

[Improve] Remove the duplication in the gitlab yaml for the First Playable

Description

Remove the duplication in the gitlab yaml (.gitlab-ci.yml) for the First Playable

We want to remove this duplication to make it easier to release different versions.

One of the things we also want to do is to get away from making releases via branching. Instead we can use the gitlab Release feature which should work via tags. https://docs.gitlab.com/ee/user/project/releases/

We can consider switching to Rules. https://docs.gitlab.com/ee/ci/yaml/#rules

The Problem

The following stages are duplicated:

  • deploy (deploy:fp)
  • build:client (build:client:fp)
  • package (package:fp)
  • containerize (containerize:fp)

Background/Current State

Hack for FP release

The way things currently work is that the branch for fp releases/firstplayable is specified in the only field of the jobs.

build:client:fp:
    ...
    only:
        - releases/firstplayable

Solution

We need to be able to:

  • parameterize - npm run build -- --mode firstplayable in the build:client or
  • Remove the need for the .env files altogether or
  • Use gitlab variables to control the build https://docs.gitlab.com/ee/ci/variables/

There will be some Frontend work

  • We need to get away from using the node .env files

Additional Information

Steps

  • Stop referencing the docker image by latest
Edited by Marc Faulise