Build CKEditor in Gitlab CI

Idea:

1. In the Gitlab pipeline we build the js artifacts for ai_ckeditor and push them to the repository
2. Gitlab is configured not to run the pipleline again because of the commit message [ci skip]

Todo:

The build runner needs access permissions to push to the Gitlab repository.

Future:

The process should be generic for all sub-modules of ai.

Something like this:

.gitlab-ci.yml

js_build:
  stage: build
  script:
    -|
      modules=$(find modules -maxdepth 1 -mindepth 1 -type d)
      for module in ${modules[@]}; do
         pushd ${module}
         if [ -f ./build.sh ]; then ./build.sh; rm -rf node_modules; fi
         popd
      done

Added one comment, but I'm not sure if it works with Drupal Gitlab. Otherwise looks good - Kevin would setup the access token.

I've added the access token under the CI variable "ACCESS_TOKEN", but there is also this in the logs on the failed job:

Run
  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.

Can we set that to a dummy Drupal CI user since it should have access via the access token to commit back?

But yes the cache key for jobs should 'work' since it is just GitLab underneath.

Actually, one thing I just realized looking at the order of the jobs - this job should run after the testing is done correctly, correct? Since its skipping CI, it would otherwise go ahead and push a build even if testing failed, if I'm not mistaken?

Or build during the build process, but not commit until after the tests.

IMO the jobs run like this:

Issue fork repository:

1. js_build - Rebuilds JS but does not commit changes and pushes, because there is no access token.
2. phpunit - Run test with rebuilt JS

The build JS is saved as an artifact and used for testing.

Main repository (after merging, or with direct commits):

1. js_build - Rebuilds JS, commits and pushes changes (if any) with an access token. The commit is run with option -o ci.skip to prevent the same pipeline from being triggered.
2. phpunit - Run test with rebuilt JS

I think this is correct. Tests are always run with the latest JS code. The latest JS code becomes part of the repository and will be part of releases.

The logic of the job looks sound to me.

Trying the merge

After some testing we got it working. Huge thank you to @breidert!

Automatically closed - issue fixed for 2 weeks with no activity.

unassigning