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.

Sign up for GitHub

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

CI TI limitation for location of codebase #9542

Merged
merged 2 commits into from
Feb 28, 2025
Merged

CI TI limitation for location of codebase #9542

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5c181bc
added TI limitation for location of codebase
nofarblue Feb 27, 2025
3f54750
Updated text around Python limitations
M-Tsur Feb 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions docs/continuous-integration/use-ci/run-tests/tests-v1/ti-for-csharp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,12 @@ Currently, TI (v1) for C# is behind the feature flag `TI_DOTNET`. Contact [Harne

## Enable TI for C#

:::note

* To use TI for C#, you must use .NET Core or NUnit.<!-- or Framework. Framework is supported on Windows [VM build infrastructures](/docs/category/set-up-vm-build-infrastructures/) only, and you must specify the [Framework build environment](#build-environment) in the YAML editor. -->
* Test Intelligence requires that the code is cloned into the default workspace directory, `/harness/`. If the code is placed elsewhere, Test Intelligence will not function correctly.

:::
You can enable TI for C# in three steps:

<!-- no toc -->
Expand All @@ -30,11 +36,7 @@ You can enable TI for C# in three steps:

Add the **Run Tests** step to the [Build stage](../../set-up-build-infrastructure/ci-stage-settings.md) in a [CI pipeline](../../prep-ci-pipeline-components.md).

:::info

To use TI for C#, you must use .NET Core or NUnit.<!-- or Framework. Framework is supported on Windows [VM build infrastructures](/docs/category/set-up-vm-build-infrastructures/) only, and you must specify the [Framework build environment](#build-environment) in the YAML editor. -->

:::

You must select **Run only selected tests** (`runOnlySelectedTests: true`) to enable Test Intelligence. For information about each setting, go to [Run Tests step settings](#run-tests-step-settings).

Expand Down
3 changes: 3 additions & 0 deletions docs/continuous-integration/use-ci/run-tests/tests-v1/ti-for-java-kotlin-scala.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,9 @@ While **Run Tests** step remains backwards compatible, Harness recommends using
:::

## Enable TI for Java, Kotlin, or Scala
:::note
Test Intelligence requires that the code is cloned into the default workspace directory, `/harness/`. If the code is placed elsewhere, Test Intelligence will not function correctly.
:::

You can enable TI for Java, Kotlin, or Scala in three steps:

Expand Down
10 changes: 6 additions & 4 deletions docs/continuous-integration/use-ci/run-tests/tests-v1/ti-for-python.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,12 @@ While **Run Tests** step remains backwards compatible, Harness recommends using

## Enable TI for Python

:::note

* To use TI for Python, the image for the step must have Python 3 installed and accessible. Additionally, Virtual Environments for Python (`venv`) are not supported by TI.
* Test Intelligence requires that the code is cloned into the default workspace directory, `/harness/`. If the code is placed elsewhere, Test Intelligence will not function correctly.
:::

You can enable TI for Python in three steps:

<!-- no toc -->
Expand All @@ -30,11 +36,7 @@ You can enable TI for Python in three steps:

Add the **Run Tests** step to the [Build stage](../../set-up-build-infrastructure/ci-stage-settings.md) in a [CI pipeline](../../prep-ci-pipeline-components.md).

:::info

To use TI for Python, your codebase must be Python 3.

:::

In the Run Tests step, you must select **Run only selected tests** (`runOnlySelectedTests: true`). For information about each setting, go to [Run Tests step settings](#run-tests-step-settings).

Expand Down
4 changes: 4 additions & 0 deletions docs/continuous-integration/use-ci/run-tests/tests-v1/ti-for-ruby.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,10 @@ While **Run Tests** step remains backwards compatible, Harness recommends using

## Enable TI for Ruby

:::note
Test Intelligence requires that the code is cloned into the default workspace directory, `/harness/`. If the code is placed elsewhere, Test Intelligence will not function correctly.
:::

You can enable TI for Ruby in three steps:

1. [Add a **Run Tests** step.](#add-the-run-tests-step) or use our new [**Test**](../tests-v2.md)
Expand Down
6 changes: 3 additions & 3 deletions docs/continuous-integration/use-ci/run-tests/tests-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,13 @@ If this feature is not yet enabled in your account, please reach out to [Harness
:::


:::info
:::note

To use TI for Python, your codebase must be Python 3.
* Test Intelligence requires that the code is cloned into the default workspace directory, `/harness/`. If the code is placed elsewhere, Test Intelligence will not function correctly.
* To use TI for Python, the image for the step must have Python 3 installed and accessible. Additionally, Virtual Environments for Python (`venv`) are not supported by TI.

:::


## Configure the Test step

Add the **Test** step to the [Build stage](/docs/continuous-integration/use-ci/set-up-build-infrastructure/ci-stage-settings.md) in a [CI pipeline](/docs/continuous-integration/use-ci/prep-ci-pipeline-components.md).
Expand Down