status-desktop/ci
Alex Jbanca 6e6693a428 chore(Qt5.15): Update windows CI Qt install script
chore(Qt5.15): Update windows Qt install script
2023-01-31 19:30:24 +02:00
..
cpp fix(CPP): fix linux compiling issues 2022-08-23 19:38:23 +02:00
Dockerfile chore: update go version in dockerfile 2022-08-03 09:40:47 -04:00
Jenkinsfile ci: add a combined Jenkinsfile for releases 2021-04-14 15:36:00 -04:00
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 chore(Qt5.15): Update windows CI Qt install script 2023-01-31 19:30:24 +02: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 add Jenkinsfiles and Dockerfile for CI 2020-07-01 22:06:37 +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 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.