status-desktop/ci
Jakub Sokołowski 97b02e1f04
chore(ci): do full Windows workspace cleanup
If we don't we regularly get weird Git failures on Windows like:
```
fatal: Unable to find current revision in submodule path 'vendor/qzxing/tests/resources'
fatal: Failed to recurse into submodule path 'vendor/qzxing'
```
Or
```
stderr: fatal: Unable to create '.../.git/index.lock': File exists.
```
Which are very annoying and require manual workspace purge by infra team.

Many of you will get annoyed with resulting slower checkouts
on subsequent builds, but that's a price I'm willing to pay.

Signed-off-by: Jakub Sokołowski <jakub@status.im>
2024-03-08 21:18:58 +01:00
..
cpp ci: cleanup more build artifacts 2024-02-28 15:56:40 +01:00
Dockerfile
Jenkinsfile
Jenkinsfile.combined chore(ci): reuse discord send function from library 2024-02-14 16:42:27 +01:00
Jenkinsfile.linux ci: cleanup more build artifacts 2024-02-28 15:56:40 +01:00
Jenkinsfile.macos ci: cleanup more build artifacts 2024-02-28 15:56:40 +01:00
Jenkinsfile.tests-nim ci: cleanup more build artifacts 2024-02-28 15:56:40 +01:00
Jenkinsfile.tests-ui ci: cleanup more build artifacts 2024-02-28 15:56:40 +01:00
Jenkinsfile.windows chore(ci): do full Windows workspace cleanup 2024-03-08 21:18:58 +01: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 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.