CI/CD Home MVC: CI linter
Release notes
CI Linter validates your pipeline syntax and provides you with detailed information about the result of each job, Previously CI linter was located on the jobs page which was difficult to access. In this release accessing the linter is easier than ever, as it is apart of the new pipeline editor, with this improvement you can easy access CI linter and quickly validate and see the details of each job before running your pipeline.
Problem to solve
From part 3 outlined in &4540 (comment 424441378).
- port the linting functionality from the CI Lint page
Proposal
"CI Lint" button on the Pipeline Editor page
The most MVC option would be to just have a button for "CI Lint" on the Pipeline Editor page, and then place a "Pipeline Editor" button to the CI Lint page so it's easy to go back.
Place CI Lint in a tab inside the editor
I think having both Validate and CI Lint tabs would be redundant, if we go this route we should at least merge the two. The Validate tab is basically the Linter without the editor (just the warnings).
However, in that case, why don't we just have the Linter in the editor tab itself? I'm guessing it's more effort to implement?
@v_mishra had a great suggestion:
How about presenting
Validate
as a button on the same header as the CI template dropdown (right hand side corner). Clicking on it could provide in-line suggestions if any or just a toast/alert if validated successfully, and it would become inactive until I make any changes to config.
It'd look something like this:
Then, we could work on offering those suggestions in-line (perhaps once we work on the problem validation for CI validation).
Links
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.