docs: fix stale references across all documentation
- ARCHITECTURE.md: fix WinRM subnet (192.168.1179), VM box shows VS 2026/Python 3.13/unzip+python build instead of .NET SDK 8/git clone/dotnet build - BEST-PRACTICES.md: fix VMnet11/192.168.11 VMnet8 NAT/192.168.79 - CI-FLOW.md: Step 3 workflow YAML updated to actual Invoke-CIJob.ps1 params (Submodules, BuildCommand, GuestArtifactSource); note that -VMIPAddress is auto-detected - OPTIMIZATION.md: BaseClean tier updated to VS BuildTools 2026, .NET SDK 10.0.203, Python 3.13.3 - gitea/workflow-example.yml: remove BUILD_VM_IP (auto-detected), replace -VMIPAddress/-Configuration with -Submodules/-BuildCommand/-GuestArtifactSource
This commit is contained in:
@@ -31,14 +31,8 @@ jobs:
|
||||
# GITEA_CI_TEMPLATE_PATH is injected by runner/config.yaml global envs
|
||||
# GITEA_CI_CLONE_BASE_DIR is injected by runner/config.yaml global envs
|
||||
|
||||
# IP address for this build VM.
|
||||
# For parallel builds, each concurrent job needs a unique IP.
|
||||
# Assign via Gitea matrix or a simple offset scheme.
|
||||
# Example: use a fixed IP per runner slot, mapped by capacity index.
|
||||
# For single concurrent builds: use one fixed IP.
|
||||
BUILD_VM_IP: "192.168.11.101"
|
||||
|
||||
# Gitea Credential Manager target (set in runner/config.yaml)
|
||||
# The VM IP is auto-detected via vmrun getGuestIPAddress — no BUILD_VM_IP needed.
|
||||
GUEST_CRED_TARGET: "BuildVMGuest"
|
||||
|
||||
steps:
|
||||
@@ -66,8 +60,9 @@ jobs:
|
||||
-RepoUrl "${{ github.server_url }}/${{ github.repository }}.git" `
|
||||
-Branch "${{ github.ref_name }}" `
|
||||
-Commit "${{ github.sha }}" `
|
||||
-Configuration "Release" `
|
||||
-VMIPAddress "$env:BUILD_VM_IP" `
|
||||
-Submodules `
|
||||
-BuildCommand 'python build_plugin.py --final --dist-dir dist' `
|
||||
-GuestArtifactSource 'dist' `
|
||||
-GuestCredentialTarget "$env:GUEST_CRED_TARGET"
|
||||
|
||||
if ($LASTEXITCODE -ne 0) {
|
||||
|
||||
Reference in New Issue
Block a user