mirror of
https://github.com/keymanapp/keyman.git
synced 2026-09-18 05:37:40 +00:00
38c2d031bb
The trigger-release-builds.sh script is not a full builder script, and does not setup all the necessary environment for using `builder_launch`. This causes a script error: ``` [resources/teamcity/triggers] ## script '/resources/build/version/build.sh ' launched... /c/BuildAgent/work/99b311828f4ee7c/keyman/resources/builder.inc.sh: line 517: _builder_build_deps: unbound variable ``` So, rolling this back to a direct call to the script, at least until we update trigger-release-builds to be a full builder script. Test-bot: skip Build-bot: skip |
||
|---|---|---|
| .. | ||
| android | ||
| common | ||
| developer | ||
| includes | ||
| ios | ||
| linux | ||
| macos | ||
| triggers | ||
| web | ||
| windows | ||
| README.md | ||
Teamcity Build Configuration Scripts
This directory contains TeamCity (TC) build scripts. Each script corresponds to a build configuration on TC.
Running scripts locally
It's possible to run some of the build locally in a Docker container. Of course this won't work for the parts, like uploading files, that require keys or other secrets.
To run locally start a Docker container:
docker run -v $(pwd):/Develop -it ubuntu:24.04 /bin/bash
(for the Linux integration tests, you'll have to pass --privileged as well.)
Inside of the container, run
apt update && apt install -y sudo
export DOCKER_RUNNING=1
echo "ubuntu ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
su ubuntu
and then run the build, e.g.
cd /Develop
resources/teamcity/linux/keyman-linux-test.sh configure,build,test