status-desktop/ci
Jonathan Rainville 7a3a984fa4 test(env-var): add TEST_ENVIRONMENT env var for test specific changes
Fixes #9210

Adds the `TEST_ENVIRONMENT` that stops banners from showing and touch id to be activated (needs to be tested by someone on Mac).

Also improves the waiting time on verifying screens. Will undo that change if it becomes flaky.

To make sure your local tests still work well and hide the banner as well, make sure to put `TEST_ENVIRONMENT=1` in the suite settings' env vars
2023-01-27 11:26:41 -05:00
..
cpp
Dockerfile
Jenkinsfile
Jenkinsfile.combined chore: up timeout time for release builds to 60min 2023-01-16 11:32:04 -05:00
Jenkinsfile.e2e test(env-var): add TEST_ENVIRONMENT env var for test specific changes 2023-01-27 11:26:41 -05:00
Jenkinsfile.imports ci: fix name of e2e test jobs in gh comments 2022-11-23 20:04:25 +01:00
Jenkinsfile.linux ci: fix name of e2e test jobs in gh comments 2022-11-23 20:04:25 +01:00
Jenkinsfile.linux-cpp ci: fix name of e2e test jobs in gh comments 2022-11-23 20:04:25 +01:00
Jenkinsfile.macos ci: update Apple dev team ID to update the org 2022-12-08 20:07:36 +01:00
Jenkinsfile.macos-cpp.todo ci: fix name of e2e test jobs in gh comments 2022-11-23 20:04:25 +01:00
Jenkinsfile.tests-nim fix(ci): make tests-nim use docker image with nim installed 2023-01-11 10:57:21 +01:00
Jenkinsfile.windows ci: fix name of e2e test jobs in gh comments 2022-11-23 20:04:25 +01:00
Jenkinsfile.windows-cpp.todo ci: fix name of e2e test jobs in gh comments 2022-11-23 20:04:25 +01:00
README.md

README.md

Description

These Jenkinsfiles are used to run CI jobs in Jenkins. You can find them here: https://ci.status.im/job/nim-status-client/

Builds

Linux

In order to build the Linux version of the application we use a modified a12e/docker-qt:5.14-gcc_64 Docker image with the addition of Git and Golang.

The image is built with Dockerfile using:

docker build -t statusteam/nim-status-client-build:latest .

And pushed to: https://hub.docker.com/r/statusteam/nim-status-client-build

MacOS

The MacOS builds are run on MacOS hosts and expect Command Line Toold and XCode to be installed, as well as QT being available under /usr/local/qt.

It also expects the presence of the following credentials:

  • macos-keychain-identity - ID of used signing certificate.
  • macos-keychain-pass - Password to unlock the keychain.
  • macos-keychain-file - Keychain file with the MacOS signing certificate.

You can read about how to create such a keychain here.