This requires to move some other files around. Also move `finalize`
and `mergeInDefaults` methods to processor and rename them to
`finalizeProcessorAction` and `mergeInOtherProcessorAction` (decided
to directly use the term `ProcessorAction`, to which `RuleBehavior`
will be renamed to in a following PR).
Co-authored-by: Marc Durdin <marc@durdin.net>
This modifies the build triggers so that changes in `resources/teamcity` don't trigger builds on all platforms anymore. If a change happened in `resources/teamcity/$platform` or `resources/teamcity/includes` it will trigger a build for `$platform`.
Since bash doesn't support negative look-aheads we use `grep` with the Perl regex option.
Fixes: #13943
This change addresses code review comments. `common` and `core` also
have TC build configs, so we add labels for them as well.
Co-authored-by: Marc Durdin <marc@durdin.net>
Previously, if we had to install a new node version, we activated it in the same subshell as the installation. This had the effect that `NVM_BIN` was set to the new version only in the subshell, but otherwise it still had the wrong value. This caused build failures. Subsequent builds would succeed because the node version was now available.
This change fixes things by using an explicit `if` instead of the construct with parens which opened another subshell.
Fixes: #14056
Previously, if we had to install a new node version, we activated it in
the same subshell as the installation. This had the effect that `NVM_BIN`
was set to the new version only in the subshell, but otherwise it still
had the wrong value. This caused build failures. Subsequent builds would
succeed because the node version was now available.
This change fixes things by using an explicit `if` instead of the
construct with parens which opened another subshell.
Fixes: #14056
Test-bot: skip
Add label `$platform` for changes to `resources/teamcity/$platform`
or `resources/teamcity/includes`.
Also remove no longer existent `linux/legacy/` paths.
Fixes: #13943
Test-bot: skip
This fixes the version numbers in `km-config` which broke with #13854. This also fixes opening the download page in `km-config` because that uses a version number in the URL.
Fixes: #14031
Follow-up-of: #13854
This modifies the build triggers so that changes in `resources/teamcity`
don't trigger builds on all platforms anymore. If a change happened in
`resources/teamcity/$platform` or `resources/teamcity/includes` it will
trigger a build for `$platform`.
Since bash doesn't support negative look-aheads we use `grep` with the
Perl regex option.
Part-of: #13943
Build-bot: skip
This are a little early but good to have in place. Per release process
wiki, this should have been done at time of 18.0 stable release but
was missed (by me).
