Implement Format Checks for Groovy Code in GitHub Actions Workflow

[karim20230]

In this change, I have implemented a new GitHub Actions workflow named "Format-checks". This workflow is triggered on every push and pull request to the 'main' branch.

This change will help to ensure that all Groovy code in the repository adheres to our coding standards and best practices, and will prevent code with formatting errors from being merged into the 'main' branch.

--failon error -The command will cause the workflow to fail if any errors are detected by GroovyLint.

[mkaapu]

Jenkins Declarative Pipeline is not exactly groovy, but simple text scripts that use a Pipeline DSL (domain-specific language) based on the Groovy programming language.
There are better option for linting Pipeline scripts and Jenkins installation itself comes with linter tool:
https://www.jenkins.io/doc/book/pipeline/development/

[karim20230]

Jenkins Declarative Pipeline is not exactly groovy, but simple text scripts that use a Pipeline DSL (domain-specific language) based on the Groovy programming language. There are better option for linting Pipeline scripts and Jenkins installation itself comes with linter tool: https://www.jenkins.io/doc/book/pipeline/development/

Yeah agreed! also npm-groovy-lint tool is designed to lint Groovy code, issues in a Jenkins Pipeline script. the tool can check Groovy code for example style issues, potential bugs, and other problems. for example Runing npm-groovy-lint with the --fix option on all files in the directory. The --fix option automatically fixes any fixable issues in the code.

[karim20230]

Although there are warnings and informational messages, there are zero errors reported.

I believe that means the code compiles and functions as intended. btw though checks fails we maybe need to improve code style!

resolved