(Re)enable linting .gitlab-ci inline scripts

Release notes

Problem to solve

As a developer, I want to lint the script parts of my .gitlab-ci.yml files, so I can find potential issues and solve them.

Intended users

• Sasha (Software Developer)
• Priyanka (Platform Engineer)
• Cameron (Compliance Manager): Any QA persona

User experience goal

Without the feature, if I as a user want to lint my inline .gitlab-ci.yml scripts, I need to copy past the script text to a separate file and run my linter on that file.

With the feature, linting my inline .gitlab-ci.yml scripts is automated. And the results can be added to the MR overview and used with policies.

Proposal

I propose to revive the disabled existing functionality as hinted here:
https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/doc/development/cicd/templates.md#syntax-guidelines

The code may have to be refurbished.

Further details

Permissions and Security

Documentation

Availability & Testing

Available Tier

Feature Usage Metrics

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

What is the competitive advantage or differentiation for this feature?

Links / references

This issue was automatically tagged with the label groupcompliance by TanukiStan, a machine learning classification model, with a probability of 0.88.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can use the @gitlab-bot label ~"group::<correct group name>" command, or leave the issue to be triaged by group leaders initially assigned by TanukiStan.

This message was generated automatically. You're welcome to improve it.

added automation:ml groupcompliance labels

added devopsgovern sectionsec labels

Hey @Valkhof, thank you for creating this issue!

To get the right eyes on your issue more quickly, we encourage you to follow the issue triage best practices.

PLEASE NOTE: You will need to use the @gitlab-bot label command to apply labels to this issue.

To set expectations, GitLab product managers or team members can't make any promise if they will proceed with this. However, we believe everyone can contribute, and welcome you to work on this proposed change, feature or bug fix. There is a bias for action, so you don't need to wait. Try and spin up that merge request yourself.

If you need help doing so, we're always open to mentor you to drive this change.

This message was generated automatically. You're welcome to improve it.

added automation:self-triage-encouraged label

I think this should be with grouppipeline execution

cc @rutshah

added grouppipeline execution label and removed groupcompliance label

removed devopsgovern label

added devopsverify label

removed sectionsec label

added sectionci label

added grouppipeline authoring label and removed grouppipeline execution label

mentioned in issue gitlab-org/quality/triage-reports#20332 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20448 (closed)

@Valkhof - I believe we have this feature enabled and it is active.

here is an example in our doc; https://gitlab.com/furkanayhan/test-project/-/blob/75c341a860d8a71853b28364e2a295f91e3aeb3d/.gitlab-ci.yml

cc @furkanayhan

mentioned in issue gitlab-org/quality/triage-reports#20585 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20753 (closed)

mentioned in issue gitlab-org/quality/triage-reports#20833 (closed)