When syntax errors are present, pipeline simulation doesn't show logical errors
Release notes
Problem to solve
When syntax errors are present, pipeline simulation doesn't show logical errors. In the below example, if config has logical errors, they will only appear once the syntax errors are fixed. It can be a confusing experience since the user might run the simulation once, see that there's only syntax errors, fix them, see "syntax is correct" in the linter status and make a commit, only to see that there are actually logical errors that lead to the pipeline failure.
Proposal
We will need a special empty/ starting state for the simulation for when syntax errors are present. The goal is to facilitate a smooth debugging flow and communicate that syntax errors need to be resolved before logical errors can be found.
Might also need to look at how we present the syntax check status, so it's clear that there still might be logical errors. My concern is that users will see the positive syntax check result and assume it means their config overall is correct, even though there may be logical errors they didn't check for.
Intended users
Feature Usage Metrics
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.