Skip to content

Commit fccced3

Browse files
committed
completely delete project-pack
1 parent 8703ac6 commit fccced3

File tree

3 files changed

+2
-48
lines changed

3 files changed

+2
-48
lines changed

.yamato/README.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,14 @@
11
# Netcode for GameObjects CI Documentation
22

33
## Overview
4-
This document provides an overview of the Continuous Integration (CI) implementation for Netcode for GameObjects.
4+
This document provides an overview of the Continuous Integration (CI) implementation for Netcode for GameObjects.
55
Specifics of each test are described within related files (for example .yamato/package-tests.yml) and this file present high level overview related to overall implementation.
66

77
## Test Configurations
88
CI related files are present inside .yamato/ folder and we can distinguish specific tests
99

1010
### Helper jobs
1111
- `.yamato/package-pack.yml` responsible for generating package artifacts (.tgz) required for testing and publishing.
12-
- `.yamato/project-pack.yml` responsible for generating package artifacts (.tgz) required for testing and publishing. This packs all packages of a given project.
1312
- `.yamato/_run-all.yml` responsible for grouping tests into groups for easier management (for example "all console tests").
1413
- `.yamato/_triggers.yml` responsible for defining triggers (PR, nightly, weekly etc.) and defining which tests to run.
1514
- `disable-burst-if-requested.py` responsible for helping to disable burst if needed.
@@ -77,4 +76,4 @@ Currently, the CI implementation supports the following platforms:
7776

7877
## Design Considerations
7978
In theory, we could manually write jobs for every configuration. However, this approach would be more error-prone, especially when modifications or fixes are needed, as it would require keeping track of all configurations.
80-
The downside of our current approach is that it can sometimes impact readability due to the use of nested if and for statements.
79+
The downside of our current approach is that it can sometimes impact readability due to the use of nested if and for statements.

.yamato/project-pack.yml

Lines changed: 0 additions & 44 deletions
This file was deleted.

.yamato/project-updated-dependencies-test.yml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,6 @@ updated-dependencies_{{ project.name }}_NGO_{{ platform.name }}_{{ editor }}:
4242
paths:
4343
- "upm-ci~/test-results/**/*"
4444
dependencies:
45-
# - .yamato/project-pack.yml#project_pack_-_{{ project.name }}_{{ platform.name }}
4645
- .yamato/package-pack.yml#package_pack_-_ngo_{{ platform.name }}
4746
{% endfor -%}
4847
{% endfor -%}

0 commit comments

Comments
 (0)