status-desktop/ci
Michał Cieślak 2853284751 Makefile: link nim tests to status-go and bump nim-tests docker image 2024-10-31 11:11:30 +01:00
..
cpp ci: move proxy stage setup to jenkins-lib 2024-08-28 10:30:43 +02:00
Dockerfile fix(status-go)_: add missing status-go dependencies (#16470) 2024-10-08 19:36:20 +05:30
Jenkinsfile
Jenkinsfile.combined ci: move proxy stage setup to jenkins-lib 2024-08-28 10:30:43 +02:00
Jenkinsfile.linux fix(ci)_: move nim cache to workspace tmp folder 2024-10-11 13:23:35 +02:00
Jenkinsfile.linux-nix fix(ci)_: move nim cache to workspace tmp folder 2024-10-11 13:23:35 +02:00
Jenkinsfile.macos fix(ci)_: move nim cache to workspace tmp folder 2024-10-11 13:23:35 +02:00
Jenkinsfile.tests-e2e chore(@ci): increase timeout for autotests for 4 minutes by default 2024-10-30 12:40:33 +03:00
Jenkinsfile.tests-nim Makefile: link nim tests to status-go and bump nim-tests docker image 2024-10-31 11:11:30 +01:00
Jenkinsfile.tests-ui ci: move proxy stage setup to jenkins-lib 2024-08-28 10:30:43 +02:00
Jenkinsfile.windows fix(ci)_: move nim cache to workspace tmp folder 2024-10-11 13:23:35 +02:00
README.md ci: upgrade docker image to Ubuntu 20.04 2023-07-03 20:50:02 +02:00

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.