erabo/spiegel-keyman
1
0
Fork 0
mirror of https://github.com/keymanapp/keyman.git synced 2026-09-10 17:47:42 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6
spiegel-keyman/resources/build
History
Marc Durdin b888a6075b fix(common): improve increment-version robustness 
Fixes #4061.

Four things:

1. Reorder the script steps so that builds are triggered before the PR
   is created. This should not really be necessary, but I am seeing some
   evidence that TeamCity is not respecting the commit sha we request to
   build. (This arose with 14.0.194 where a build agent became
   unavailable during a build and TC cancelled and restarted the build,
   but from a later revision... which this particular fix may not help,
   I guess...)
2. Add debug logging so we can see exactly which commit sha that we
   send to TeamCity
3. Handle errors in version increment by aborting the script with an
   error.
4. Add a -f force mode which we can use to trigger a build even if no
   changes are detected. This will need a corresponding patch in TC.
2020-12-03 10:24:19 +11:00
..
history chore(ci): address review comment 2020-02-04 12:12:07 +11:00
l10n chore(common/resources): Clean up README 2020-12-02 11:21:06 +07:00
version fix(common): improve increment-version robustness 2020-12-03 10:24:19 +11:00
build-download-resources.sh feat(android): Use build-download-resources.sh for KMApro and FV apps 2020-07-08 14:03:02 +07:00
build-utils.sh fix(android): export all the VERSION vars 2020-08-06 11:40:21 +07:00
increment-version.sh fix(common): improve increment-version robustness 2020-12-03 10:24:19 +11:00
jq-license.txt fix(common): build check failed 2020-03-18 14:55:37 +11:00
jq-win64.exe chore(common/resources): use shared scopes definition 2020-05-19 17:08:57 +10:00
jq.inc.sh fix(windows): support jq-win64 2020-04-29 12:41:07 +10:00
README.md chore(common): improve build README.md 2020-11-04 08:54:28 +11:00
run-required-test-builds.sh chore(common/resources): cleanup script filenames 2020-05-19 17:39:17 +10:00
sentry-control.inc.sh chore(common/resources): cleanup script filenames 2020-05-19 17:39:17 +10:00
trigger-builds.inc.sh fix(common): improve increment-version robustness 2020-12-03 10:24:19 +11:00
trigger-definitions.inc.sh docs(common/resources): update outdated comment 2020-05-20 09:25:25 -06:00
vswhere-LICENSE.txt fix(common): enable build for win x64 and use global VERSION.md 2020-05-04 15:06:08 +10:00
vswhere.exe fix(common): enable build for win x64 and use global VERSION.md 2020-05-04 15:06:08 +10:00
xcode-utils.sh fix(ios): use environment and version-with-tag for sentry 2020-04-28 11:35:59 +10:00

README.md

Release builds

A release is triggered nightly whenever a pull request has been merged to the branch; it runs from a TeamCity build configuration that runs increment-version.sh and then uploads the resulting HISTORY.md to https://downloads.keyman.com/history/HISTORY.md.

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...

Various tools

vswhere.exe is used by Keyman Core to select a Visual Studio version on Windows. Official source: https://github.com/microsoft/vswhere License

jq-win64.exe is used by various builds for json query. Official source: License