Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add check for IsMainRepository #23

Open
gep13 opened this issue Mar 17, 2022 · 0 comments
Open

Add check for IsMainRepository #23

gep13 opened this issue Mar 17, 2022 · 0 comments
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality

Comments

@gep13
Copy link
Member

gep13 commented Mar 17, 2022

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.

@gep13 gep13 added the Feature Issues that introduce new functionality to the project, instead of updating existing functionality label Mar 17, 2022
@gep13 gep13 added this to the Future milestone Mar 17, 2022
@gep13 gep13 removed this from the Future milestone Mar 17, 2022
gep13 added a commit that referenced this issue May 8, 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.
gep13 added a commit that referenced this issue May 8, 2022
* release/0.12.0:
  (#23) Add support for integration tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Issues that introduce new functionality to the project, instead of updating existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant