Document manual NinjaOne rollout for v1.2.3
Some checks failed
OfficeCom Sentinel Client / build-client (push) Has been cancelled

This commit is contained in:
OfficeCom Codex
2026-07-17 01:00:34 +02:00
parent b5e06b885a
commit e8b7a2831d

View File

@@ -17,7 +17,7 @@ Build these locally with:
```powershell ```powershell
powershell -ExecutionPolicy Bypass -File .\build\build-client-package.ps1 powershell -ExecutionPolicy Bypass -File .\build\build-client-package.ps1
powershell -ExecutionPolicy Bypass -File .\build\build-release-manifest.ps1 ` powershell -ExecutionPolicy Bypass -File .\build\build-release-manifest.ps1 `
-ArtifactUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v2.0.0/OCSentinelClient-win-x64.zip" -ArtifactUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/OCSentinelClient-win-x64.zip"
``` ```
## Installed Layout ## Installed Layout
@@ -36,7 +36,7 @@ Initial install/update:
```powershell ```powershell
& "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" ` & "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" `
-ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v2.0.0/version.json" ` -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json" `
-Force -Force
``` ```
@@ -44,7 +44,7 @@ Routine update:
```powershell ```powershell
& "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" ` & "C:\Program Files\OCSentinel\scripts\update-ocsentinel.ps1" `
-ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v2.0.0/version.json" -ManifestUrl "https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json"
``` ```
Runtime: Runtime:
@@ -65,3 +65,21 @@ Runtime:
This writes: This writes:
- `C:\ProgramData\OCSentinel\secrets\ocsentinel-upload-secret.dat` - `C:\ProgramData\OCSentinel\secrets\ocsentinel-upload-secret.dat`
## Current Manual Release State
As of July 16, 2026, the first manual release is already published:
- tag: `v1.2.3`
- release URL: `https://gitea.officecom.cloud/officecom/oc-sentinel/releases/tag/v1.2.3`
- manifest URL: `https://gitea.officecom.cloud/officecom/oc-sentinel/releases/download/v1.2.3/version.json`
This means NinjaOne rollout can start immediately without waiting for a Gitea runner.
## Later Automation
When a Gitea runner is added later, the usual next step is:
1. connect to the runner host through SSH or RDP, depending on the server type
2. install and register the Gitea runner
3. let `.gitea/workflows/client-build.yml` publish future release artifacts automatically