History

B.Melnik a1a2f2f4e2 Remove it: add V=1 option for tests		2021-07-19 13:46:19 -04:00
..
Dockerfile	build: use same container as Jenkins CI for local packaged builds on Linux	2021-04-27 13:49:46 -05:00
Jenkinsfile	ci: add a combined Jenkinsfile for releases	2021-04-14 15:36:00 -04:00
Jenkinsfile.combined	ci: do no delete non-draft releases	2021-06-07 10:18:01 -04:00
Jenkinsfile.linux	build: on Linux use tar+gzip to preserve +x attribute of .AppImage	2021-06-07 14:26:28 -04:00
Jenkinsfile.macos	ci: do no delete non-draft releases	2021-06-07 10:18:01 -04:00
Jenkinsfile.windows	Remove it: add V=1 option for tests	2021-07-19 13:46:19 -04: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.