jenkinsfile-validator

To validate a Jenkinsfile, run the shell script locally to check for structural and syntax errors. This catches issues in both Declarative and Scripted pipelines before they cause failures in your CI environment.

Yes, you can lint Jenkins Shared Library files by validating the groovy scripts. The tool checks `vars/*.groovy` and `src/**/*.groovy` files to enforce performance, security, and maintainability best practices.

Checking a Jenkins pipeline script for hardcoded credentials requires a security audit. The validation process detects exposed secrets and hardcoded credentials within your Jenkinsfile to mitigate potential security risks.

Yes, Jenkinsfile validation works for both Declarative and Scripted pipelines. It analyzes the syntax and structure of either format, ensuring comprehensive local analysis without needing a running Jenkins server.

Running a local Jenkinsfile linter catches syntax errors, best practice violations, and security vulnerabilities early. This prevents broken pipeline executions and ensures your scripts adhere to team standards before committing code.