From f019b33a4e40ad76589b1b9f7eff2f327953d894 Mon Sep 17 00:00:00 2001 From: Dandaedre Date: Tue, 15 Sep 2026 15:27:56 +0200 Subject: [PATCH] Jenkinsfile --- Jenkinsfile | 126 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 126 insertions(+) create mode 100644 Jenkinsfile diff --git a/Jenkinsfile b/Jenkinsfile new file mode 100644 index 0000000..75e668b --- /dev/null +++ b/Jenkinsfile @@ -0,0 +1,126 @@ +// Add this webhook in Gitea: +// http://192.168.1.37:8080/gitea-webhook/post + +pipeline { + agent { label 'rust_no_docker' } + + options { disableConcurrentBuilds() } + + environment { + CARGO_TERM_COLOR = 'always' + + CI_ARTIFACT_DIR = '.ci-artifacts' + } + + stages { + stage('Checkout') { + steps { + checkout scm + } + } + + stage('Validate Repository') { + steps { + sh ''' + set -eu + + echo "Validating Win Diagnostics repository..." + + test -f README.md + test -f LICENSE + test -f AGENT.md + + echo "Repository structure OK." + ''' + } + } + + /* + * Windows collection is intentionally NOT run here. + * + * This Jenkins agent is not the target Windows machine. + * + * Collection scripts should eventually receive separate + * Windows-specific validation if a suitable CI worker becomes + * available. + */ + + /* + * TODO: Validate Diagnostic Schema + * + * Once schemas/diagnostic.schema.json exists: + * + * - validate the schema; + * - validate sanitized fixtures; + * - verify schema_version handling. + */ + + /* + * TODO: Analysis Tests + * + * Once sanitized diagnostic fixtures exist: + * + * fixtures/ + * + * run the analysis engine against them. + * + * This should be platform-independent wherever practical. + */ + + /* + * TODO: Regression Tests + * + * Known diagnostic inputs should produce expected findings, + * severity and evidence relationships. + */ + + /* + * No rendering or publishing stages belong here. + * + * Win Diagnostics produces structured diagnostic information. + * It does not own reports or PDFs. + */ + } + + post { + success { + publishChecks( + conclusion: 'SUCCESS', + name: 'Win Diagnostics CI', + summary: 'Win Diagnostics passed all currently implemented CI checks.', + text: 'Repository validation completed successfully. Diagnostic schema and fixture analysis will be enabled as they are implemented.', + title: 'Win Diagnostics CI passed' + ) + + echo '✅ Win Diagnostics CI passed.' + } + + failure { + publishChecks( + conclusion: 'FAILURE', + name: 'Win Diagnostics CI', + summary: 'Win Diagnostics failed CI.', + text: 'A repository or validation check failed. Check the Jenkins log.', + title: 'Win Diagnostics CI failed' + ) + + echo '❌ Win Diagnostics CI failed.' + } + + unstable { + publishChecks( + conclusion: 'ACTION_REQUIRED', + name: 'Win Diagnostics CI', + summary: 'Win Diagnostics CI is unstable.', + text: 'The Jenkins build completed with an unstable status.', + title: 'Win Diagnostics CI unstable' + ) + + echo '⚠️ Win Diagnostics CI is unstable.' + } + + always { + echo 'CI finished.' + } + } +}