Jakub Sokołowski
655097e2a2
This adds a `Publish` stage to the combined `Jenkinsfile` which when the `PUBLISH` parameters is true pushes a __draft__ release to GitHub. The job remembers the last value of `PUBLISH` parameter selected. The release uses the contents of the `VERSION` file at the root of the repo as the name for the release, and leaves the contents to be filled in by whoever will approve the release. The automation overwrites - or to be exact, deletes and recreates - the release, so releated builds for the same release will simply re-create it. All the built artifacts are included in the release. Signed-off-by: Jakub Sokołowski <jakub@status.im> |
||
---|---|---|
.. | ||
Dockerfile | ||
Jenkinsfile | ||
Jenkinsfile.combined | ||
Jenkinsfile.linux | ||
Jenkinsfile.macos | ||
Jenkinsfile.windows | ||
README.md |
README.md
Description
These Jenkinsfile
s 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.