status-desktop/ci
Jakub Sokołowski 2a330c5c33
ci: Discord notification for master build failrues
To make this not send 3 separate notifications for each platform we
build for I've created a special job just for building `master` branch:
https://ci.status.im/job/status-desktop/job/master/

For more details see:
https://plugins.jenkins.io/discord-notifier/

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2022-07-26 18:51:25 +02:00
..
cpp chore(CPP): foundation for user onboarding 2022-07-07 23:23:09 +02:00
Dockerfile fix: add qtlottie to linux build 2022-03-10 14:12:11 -04:00
Jenkinsfile ci: add a combined Jenkinsfile for releases 2021-04-14 15:36:00 -04:00
Jenkinsfile.combined ci: Discord notification for master build failrues 2022-07-26 18:51:25 +02:00
Jenkinsfile.linux ci: remove caching of dependencies 2022-04-15 12:45:27 +02:00
Jenkinsfile.linux-cpp.todo chore(CPP): foundation for user onboarding 2022-07-07 23:23:09 +02:00
Jenkinsfile.mac-cpp.todo chore(CPP/CI): basic CI setup for linux cmake build 2022-07-01 14:41:28 +02:00
Jenkinsfile.macos ci: bump macos job timeout to 25 minutes 2022-07-01 11:52:49 +02:00
Jenkinsfile.windows ci: remove caching of dependencies 2022-04-15 12:45:27 +02:00
Jenkinsfile.windows-cpp.todo chore(CPP/CI): basic CI setup for linux cmake build 2022-07-01 14:41:28 +02: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.