Skip to content

Feature/add ci validation tests

Description

This MR aims to add some CI validation tests. These tests execute a nominal use case of the tool on Windows & Linux.

The CI jobs are configured to run only if :

  • Run manually from the CI/CD section of the GitLab project
  • The content of the publish directory has changed

The CI pipeline is composed of 2 stages: Clean & Test. The first stage cleans the issues from the dummy test projects. The second one run the nominal execution of the tool.

Jobs are configured through environment variables. Public variables are defined at the top of the .gitlab-ci.yml file while secret ones are defined in GitLab CI masked variables.

The expected secret variables are :

  • TRELLO_KEY
  • TRELLO_TOKEN
  • GITLAB_TOKEN

Outcome

The issue that I have described here is present in the Linux CI job.

It looks like the tool does not return any exit codes 1 when failing. Therefore, the CI jobs might succeed even in case of failures.

To do

Before merging, may I ask you to create two more dummy GitLab projects like this one ? And then update these values in the .gitlab-ci.yml file ?

WIN64_GITLAB_PROJECT: 24716426
WIN32_GITLAB_PROJECT: 24716688
LINUX_GITLAB_PROJECT: 24716703

Side stuff

I took the liberty of tracking the binary files (e.g. exe, dll, lib, etc) as LFS. Which is a good practice not to commit binary files as source code.

Edited by Benoit Vander Stappen

Merge request reports

Loading