You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a build, we need to find a way of ensuring that the CI build is happening on the source repository for the code, and not for example a fork of the repository. This is needed in order to make decisions about which tasks are executed on any given CI build.
This functionality previously existed in the Recipe, but it was removed in this issue due to the fact that things work differently in TeamCity, compared to say AppVeyor.
The text was updated successfully, but these errors were encountered:
gep13
added
the
Feature
Issues that introduce new functionality to the project, instead of updating existing functionality
label
Mar 17, 2022
Introduce a new argument, testExecutionType, which can be set to either
unit, integration, or all, to control which test assemblies are exectued.
This controls the TestAssemblyFilePattern, which sets the globbing
pattern used to locate the test assemblies.
The default for this will be unit tests, but when required, this can be
set higher to execute additional tests.
When running a build, we need to find a way of ensuring that the CI build is happening on the source repository for the code, and not for example a fork of the repository. This is needed in order to make decisions about which tasks are executed on any given CI build.
This functionality previously existed in the Recipe, but it was removed in this issue due to the fact that things work differently in TeamCity, compared to say AppVeyor.
The text was updated successfully, but these errors were encountered: