spiegel-keyman/resources/teamcity/triggers
Marc Durdin 38c2d031bb maint(resources): roll back builder_launch for trigger-release-builds.sh
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
2025-12-08 07:30:49 +01:00
..
README.md maint(resources): move build trigger scripts into resources/teamcity 2025-08-27 07:28:24 +02:00
trigger-release-builds.sh maint(resources): roll back builder_launch for trigger-release-builds.sh 2025-12-08 07:30:49 +01:00
trigger-test-builds.sh maint(resources): further logging and fix indirection bug with watch 2025-10-06 16:55:02 +02:00

Release builds

A release is triggered nightly whenever a pull request has been merged to the master (alpha) or beta branches; it runs from a TeamCity build configuration that runs trigger-release-builds.sh and then uploads the resulting HISTORY.md to https://downloads.keyman.com/history/HISTORY.md.

For stable releases, these are always manually triggered in TeamCity.

To manually make a release (for example if a build falls over for a transient error or there was a build configuration problem), create a new PR that targets the branch, merge it, and then run the Trigger Release Builds build configuration for that branch. If you have no changes, see that as an opportunity to improve documentation, including this file...

Test builds

Test builds are triggered for any commit to a PR, via trigger-test-builds.sh.