erabo/spiegel-keyman
1
0
Fork 0
mirror of https://github.com/keymanapp/keyman.git synced 2026-11-06 07:57:43 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
spiegel-keyman/resources/teamcity/triggers/README.md
Marc Durdin 7390cc66aa maint(resources): move build trigger scripts into resources/teamcity 
This also removes the need to have a test for `-b` parameter in
trigger-test-builds.sh, because the TC scripts calling this can already
factor that in.

Testing script trigger so only do builds of common to verify

Fixes: #14483
Test-bot: skip
Build-bot: skip:all build:common
2025-08-27 07:28:24 +02:00

854 B
Executable file
Raw Blame History

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.