3 Commits
Author SHA1 Message Date
me0nline 42f01addca docs: document 25 unit tests and tripartite release options in root README.md
CI Test Suite / Run Component Tests & Pipeline Verification (push) Successful in 2m21s
2026-09-04 23:23:08 +02:00
me0nline a9f096ef1b ci(windows): optimize tag triggers and add default v2.0.0 tag to release-windows.yml 2026-09-04 23:22:52 +02:00
me0nline 26d3d59812 ci(linux): optimize tag triggers and add default v2.0.0 tag to release-linux.yml 2026-09-04 23:22:38 +02:00
3 changed files with 31 additions and 18 deletions
+3 -6
View File
@@ -1,18 +1,15 @@
name: Release Linux Binaries
on:
release:
types: [published, created]
push:
tags:
- '*'
- '**'
- 'v*'
workflow_dispatch:
inputs:
tag:
description: 'Release tag (optional)'
description: 'Release tag to publish assets to (default: v2.0.0)'
required: false
default: 'v2.0.0'
jobs:
release-linux:
@@ -40,6 +37,6 @@ jobs:
GITEA_TOKEN: ${{ secrets.TAG_TOKEN || github.token }}
GITEA_SERVER_URL: ${{ github.server_url }}
GITEA_REPOSITORY: ${{ github.repository }}
GITEA_REF_NAME: ${{ github.event.release.tag_name || inputs.tag || github.ref_name }}
GITEA_REF_NAME: ${{ inputs.tag || github.event.release.tag_name || github.ref_name }}
run: |
python3 compilation/upload_release.py --skip-build
+4 -6
View File
@@ -1,22 +1,20 @@
name: Release Windows Binaries & Installers
on:
release:
types: [published, created]
push:
tags:
- '*'
- '**'
- 'v*'
workflow_dispatch:
inputs:
tag:
description: 'Release tag (optional)'
description: 'Release tag to publish assets to (default: v2.0.0)'
required: false
default: 'v2.0.0'
jobs:
release-windows:
name: Build & Release Windows Binaries & Installers
# Note: Requires a registered Gitea Act Runner with label 'windows-latest'
runs-on: windows-latest
steps:
- name: Checkout Repository
@@ -77,7 +75,7 @@ jobs:
GITEA_TOKEN: ${{ secrets.TAG_TOKEN || github.token }}
GITEA_SERVER_URL: ${{ github.server_url }}
GITEA_REPOSITORY: ${{ github.repository }}
GITEA_REF_NAME: ${{ github.event.release.tag_name || inputs.tag || github.ref_name }}
GITEA_REF_NAME: ${{ inputs.tag || github.event.release.tag_name || github.ref_name }}
run: |
$py = "python"
if (-not (Get-Command "python" -ErrorAction SilentlyContinue)) {
+24 -6
View File
@@ -343,10 +343,11 @@ LOGAR/
```bash
python -m unittest discover -s tests -v
```
Runs all **22 unit tests**, covering:
Runs all **25 unit tests**, covering:
- Dynamic Root CA generation and server TLS certificate issuance.
- Dynamic client certificate issuance with CN and authority key extensions.
- Enrollment secret authentication, seat limits, and certificate revocation.
- Proactive certificate validity checks, Root CA auto-renewal, and in-flight server SSLContext reload.
- Windows & Linux event log collection, deduplication, and mTLS certificate verification.
- 12-hour evaluation window and 4-run rule progression.
@@ -365,13 +366,30 @@ Tests client enrollment, secret rejection, mTLS TLS 1.3 socket handshake, warnin
---
## Automated Releases via Gitea Actions
## Releases & Binary Distribution
Releases are triggered automatically on tag push (`v*`):
Releases can be built and published through three complementary channels:
### 1. Tag Push Automation (Gitea Actions)
Pushing a release tag automatically triggers the build workflows:
```bash
git tag v2.0.0
git push origin v2.0.0
```
Two dedicated workflows run in parallel:
- **`release-linux.yml`** (`ubuntu-latest`): Compiles `Linux_Client.bin` and `Server.bin`, generating checksums.
- **`release-windows.yml`** (`windows-latest`): Compiles `Win_Client.exe` and `Server.exe`, builds Inno Setup installers (`LOGAR-Client-Setup.exe`, `LOGAR-Server-Setup.exe`), and uploads all artifacts.
- **`release-linux.yml`** (`ubuntu-latest`): Compiles standalone native ELF binaries (`Linux_Client.bin`, `Server.bin`) and checksums.
- **`release-windows.yml`** (`windows-latest`): Compiles Windows executables (`Win_Client.exe`, `Server.exe`), builds Inno Setup installers, and publishes checksums (requires self-hosted Windows Act Runner).
### 2. Manual Workflow Dispatch (Gitea UI)
Workflows can be manually triggered on demand from the Gitea web interface:
1. Navigate to **Actions** $\rightarrow$ **Release Linux Binaries** (`release-linux.yml`).
2. Click **Run workflow**, set the release tag (defaults to `v2.0.0`), and run.
### 3. Native Local Windows Build & Direct Release Upload
For environments without a registered Windows CI runner, Windows executables can be built and published directly to Gitea releases:
```powershell
# 1. Build Windows binaries locally
python compilation/package_dist.py --target windows
# 2. Upload assets and release notes directly to the Gitea release
python compilation/upload_release.py --tag v2.0.0 --token <GITEA_TOKEN> --skip-build
```