7a3a984fa4
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 |
||
---|---|---|
.. | ||
cpp | ||
Dockerfile | ||
Jenkinsfile | ||
Jenkinsfile.combined | ||
Jenkinsfile.e2e | ||
Jenkinsfile.imports | ||
Jenkinsfile.linux | ||
Jenkinsfile.linux-cpp | ||
Jenkinsfile.macos | ||
Jenkinsfile.macos-cpp.todo | ||
Jenkinsfile.tests-nim | ||
Jenkinsfile.windows | ||
Jenkinsfile.windows-cpp.todo | ||
README.md |
README.md
Description
These Jenkinsfile
s 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.