status-desktop/ci
Jakub Sokołowski 2c5eeea503
feat(ci): add USE_MOCKED_KEYCARD_LIB parameter
It will default to `true` for Linux builds except release ones.
This setting can always be overriden manually for any build.

Resolves:
https://github.com/status-im/status-desktop/issues/12412

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2023-10-13 09:02:45 +02:00
..
cpp ci: use new Alchemy API keys for Ethereum 2023-10-05 10:29:48 -03:00
Dockerfile
Jenkinsfile
Jenkinsfile.combined ci: use new Alchemy API keys for Ethereum 2023-10-05 10:29:48 -03:00
Jenkinsfile.linux feat(ci): add USE_MOCKED_KEYCARD_LIB parameter 2023-10-13 09:02:45 +02:00
Jenkinsfile.macos feat(ci): add USE_MOCKED_KEYCARD_LIB parameter 2023-10-13 09:02:45 +02:00
Jenkinsfile.tests-e2e chore(e2e): rename TEST_ENVIRONMENT to STATUS_RUNTIME_TEST_MODE 2023-10-13 09:02:44 +02:00
Jenkinsfile.tests-nim ci: use new Alchemy API keys for Ethereum 2023-10-05 10:29:48 -03:00
Jenkinsfile.tests-statusq ci: use new Alchemy API keys for Ethereum 2023-10-05 10:29:48 -03:00
Jenkinsfile.windows feat(ci): add USE_MOCKED_KEYCARD_LIB parameter 2023-10-13 09:02:45 +02: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 the ubuntu:20.04 Docker image where we install the Qt 5.15.2 provided by aqt, linuxdeployqt provided by https://github.com/probonopd/linuxdeployqt and other dependencies (go, cmake, gcc etc.). We're using Ubuntu 20.04 to ensure glibc compatibility with the oldest still-supported LTS release and to comply with linuxdeployqt requirements.

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.