Skip to content

feat(rule): Scan Azure Pipeline YAML/JSON #7846

@sergiomarotco

Description

@sergiomarotco

Is your feature request related to a problem? Please describe.
It would be great to have a few linting rules for Azure pipeline files.
For example:

  • it would be nice to recommend adding the parameter fetchdept: 1 to the job checkout, as this can significantly speed up the checkout process.
  • searching for open tags but not closed ones, for example, I've noticed that if I write dependsOn: and then don't specify any dependencies, but instead start writing other commands like variables: or others, everything works fine, but the dependsOn: section remains incomplete.

Describe the solution you'd like
Out-of-the-Box Rules for Finding Errors in Azure CI/CD

Describe alternatives you've considered
no

Additional context
I'm willing to share my regular expressions and cases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    azurePR related with Azure CloudcommunityCommunity contributionfeature requestCommunity: new feature request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions