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 089ee7ee80 ci: scripts/sign-windows-bin.sh for signing Windows binaries 
This introduces the `scripts/sign-windows-bin.sh` script which is used
by the `Makefile` to sign application libraries and executables. It also
implements the logic necessary to distinguish between different types of
builds: release and non-release builds.

Some other changes:

* Refactore the `Makefile` target that creates the Windows ZIP to make less verbose.
* Added `Microsoft.VisualStudio.Component.Windows10SDK.10240` to VisualStudio component
* Added `BUILD_TYPE` parameter to `Jenkinsfile`s for different platform builds

Signed-off-by: Jakub Sokołowski <jakub@status.im>
 		2021-04-28 18:19:17 +02: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: scripts/sign-windows-bin.sh for signing Windows binaries 2021-04-28 18:19:17 +02:00
Jenkinsfile.linux ci: scripts/sign-windows-bin.sh for signing Windows binaries 2021-04-28 18:19:17 +02:00
Jenkinsfile.macos ci: scripts/sign-windows-bin.sh for signing Windows binaries 2021-04-28 18:19:17 +02:00
Jenkinsfile.windows ci: scripts/sign-windows-bin.sh for signing Windows binaries 2021-04-28 18:19:17 +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.