status-im
/
status-desktop
mirror of https://github.com/status-im/status-desktop.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-desktop/ci
History
Anastasiya Semenkevich 9a17498149 ci: adding more output for pytest when running tests 2024-08-19 20:42:53 +03:00
..
cpp ci: add api proxy stage build parameter 2024-08-15 16:02:46 +02:00
Dockerfile chore: bump go to 1.21 (#14946) 2024-05-30 17:08:31 +05:30
Jenkinsfile
…
Jenkinsfile.combined ci: add api proxy stage build parameter 2024-08-15 16:02:46 +02:00
Jenkinsfile.linux ci: set proxy env differently 2024-08-15 17:04:50 +02:00
Jenkinsfile.linux-nix ci: set proxy env differently 2024-08-15 17:04:50 +02:00
Jenkinsfile.macos ci: set proxy env differently 2024-08-15 17:04:50 +02:00
Jenkinsfile.tests-e2e ci: adding more output for pytest when running tests 2024-08-19 20:42:53 +03:00
Jenkinsfile.tests-nim ci: add api proxy stage build parameter 2024-08-15 16:02:46 +02:00
Jenkinsfile.tests-ui ci: add api proxy stage build parameter 2024-08-15 16:02:46 +02:00
Jenkinsfile.windows ci: set proxy env differently 2024-08-15 17:04:50 +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.