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
Jakub Sokołowski 4f60c31282
ci: use cleanup instead of always step in post steps 
Simply appropriate.
https://www.jenkins.io/doc/book/pipeline/syntax/#post

Signed-off-by: Jakub Sokołowski <jakub@status.im>
 		2022-10-26 13:45:48 +02:00
..
cpp fix(CPP): fix linux compiling issues 2022-08-23 19:38:23 +02:00
mailserver chore: setup a mailserver as part of UI tests run in CI 2022-10-03 16:31:23 -04:00
Dockerfile chore: update go version in dockerfile 2022-08-03 09:40:47 -04:00
Jenkinsfile
…
Jenkinsfile.combined ci: fix upload speeds on Windows 2022-09-15 11:41:12 +02:00
Jenkinsfile.linux ci: use cleanup instead of always step in post steps 2022-10-26 13:45:48 +02:00
Jenkinsfile.linux-cpp ci: use cleanup instead of always step in post steps 2022-10-26 13:45:48 +02:00
Jenkinsfile.macos ci: use cleanup instead of always step in post steps 2022-10-26 13:45:48 +02:00
Jenkinsfile.macos-cpp.todo ci: use cleanup instead of always step in post steps 2022-10-26 13:45:48 +02:00
Jenkinsfile.uitests ci: use cleanup instead of always step in post steps 2022-10-26 13:45:48 +02:00
Jenkinsfile.windows ci: use cleanup instead of always step in post steps 2022-10-26 13:45:48 +02:00
Jenkinsfile.windows-cpp.todo ci: use cleanup instead of always step in post steps 2022-10-26 13:45:48 +02:00
README.md
…

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.