[doc] auto-release pipelines are not triggered when using CI_JOB_TOKEN authentication

Describe the bug

When using CI_JOB_TOKEN for authentication, auto-release pipelines are not triggered.

see: https://docs.gitlab.com/ci/jobs/ci_job_token/#the-semantic-release-tool-and-job-tokens

This should be stated in the template documentation.

Expected behavior

CI_JOB_TOKEN allows for better security and less burden with access token rotation : when making the decision it should be clear what the downsides of switching. The template documentation should call the attention of the user on the fact that auto-release pipeline won't trigger in that case.

Actual behavior

The template user switches to CI_JOB_TOKEN authentication and does not understand why auto-release pipelines are not triggered anymore.

Logs and/or screenshots

n/a

Context & Configuration

Link to a project, pipeline or job facing the bug: (please provide one if possible)

The issue was reproduced using:

  • Version of the template: 4.2.1
  • GitLab server(s): Sel-managed CE instance
  • GitLab runner(s): n/a

Here is the .gitlab-ci.yml file:

include:
  - component: $CI_SERVER_FQDN/to-be-continuous/pre-commit/gitlab-ci-pre-commit@1.5.0
  - component: $CI_SERVER_FQDN/to-be-continuous/semantic-release/gitlab-ci-semrel@4.2.1
    inputs:
      changelog-enabled: true
      auto-release-enabled: true
      commit-message: "chore(release): $${nextRelease.version} [skip ci on prod]"
  - component: $CI_SERVER_FQDN/to-be-continuous/terraform/gitlab-ci-terraform@9.2.1
    inputs:
      fmt-enabled: true
      tflint-disabled: true
      publish-enabled: true
      module-system: google
      module-files: "*.tf *.md modules/*/*.tf modules/*/*.md examples/*.tf examples/*.md"

Configured GitLab CI project or group variables:

n/a

Edited by Alexis Deruelle