test: validate historian TLS migration against isolated source
This commit is contained in:
@@ -45,12 +45,22 @@ and guard exits, run the full owning project, and complete the consumer solution
|
||||
build/review before issue 131 is closed. The patch is transport-only and can be
|
||||
applied independently of the OPC UA SDK 2 rollout.
|
||||
|
||||
If release availability lags, validate only in an archived staging copy: materialize
|
||||
exact HG commit e432191 with `git archive`, pack both packages with the local-only
|
||||
version `1.0.0-validation.131`, set an isolated `NUGET_PACKAGES`, and map only those
|
||||
two package IDs to a task-local feed. Apply the future patch to a separate consumer
|
||||
archive, then replace ONLY its two package pins with the validation prerelease.
|
||||
Never pack/build the user's HG checkout, publish these validation packages, place
|
||||
them in the normal NuGet cache, or pass prerelease validation off as stable-release
|
||||
verification. Local validation and release availability results are recorded in
|
||||
`RESULTS.md` when the run completes.
|
||||
For isolated validation, use a fresh output directory OUTSIDE both repositories
|
||||
so the archived HG projects do not inherit the consumer's central package policy:
|
||||
|
||||
```bash
|
||||
python3 scripts/validation/historiangw-131/validate.py \
|
||||
--consumer-root "$PWD" \
|
||||
--hg-root /Users/dohertj2/Desktop/HistorianGateway \
|
||||
--output /tmp/historiangw-131-fresh-validation
|
||||
```
|
||||
|
||||
The script checks both live feed indexes. If both actual stable 1.0.0 packages are
|
||||
available, it validates them in an archived consumer copy. Otherwise it archives
|
||||
exact HG commit e432191 and temporarily replaces ONLY the archived Gateway csproj's
|
||||
two package references with source project references. This equivalent source
|
||||
validation does not create or publish any fake package/version. Restore uses an
|
||||
independent copy-on-write/copy cache, isolated HTTP cache and CLI home. Neither
|
||||
user checkout is built or edited. Full owning-suite TRX, required TLS failure
|
||||
classification, command exits and execution guard are retained under the task
|
||||
output. Never treat source validation as stable published-package verification.
|
||||
|
||||
Reference in New Issue
Block a user