Online Jenkinsfile Validator

Purpose: The tool validates Jenkinsfiles written in Groovy for Jenkins pipelines, covering Declarative and Scripted styles, delivering actionable diagnostics with line references. It does not execute the pipeline.

Core logic: It employs a Groovy-aware parser or AST-based checks, plus a lightweight rule engine for DSL patterns. Required features include syntax validation, brace and parenthesis matching, and detection of missing top-level blocks (e.g., pipeline for Declarative) and basic stage/steps validation. Optional features include detection of deprecated syntax and basic anti-pattern alerts. Outputs are structured diagnostics with location and severity, suitable for automation.

Inputs & Outputs: Input is a single Jenkinsfile text field (required); outputs include a list of diagnostics (type, message, line, column), an overall success flag, and a human-friendly summary for reviews.

Algorithms & Calculations: The validator uses a Groovy parser/AST when feasible, or targeted regex checks for performance. It enforces Declarative rules (agent, stages, steps) and scripted balance of braces, providing line/column locations and a severity score for each issue.

Error & Edge Cases: Very large files or unusual Groovy constructs may yield partial diagnostics. If parsing fails entirely, syntax errors are reported. Plugin-specific semantics and runtime behavior are outside scope.

Industry/Region & Localization: Jenkins Pipeline DSL is language- and region-agnostic; no localization or currency handling is applied.

Assumptions & Exclusions: Assumes Jenkinsfile uses Groovy-based syntax and common Pipeline DSL; excludes runtime execution, plugin semantics, and environment configuration validation.