Support input scenario for Pipeline Editor validation
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
We should provide options that would allow users to Validate their CI/CD config and provide specific conditions for the rules, only, except, and needs parameters. At the moment, validating the CI/CD config would apparently only use the existing contents of the scenario so it might be useful to have some form of input like toggle options based on the rules/conditions.
As an example, given the following config:
stages:
- build
build-if-file-exists:
stage: build
script:
- echo "hello"
rules:
- exists:
- dev/**/*.txt
When we use the Validate option, we should allow the user to test for both cases:
- Case 1:
dev/test/file.txtexist - Case 2:
dev/test/file.txtdoesn't exist
Example Project: https://gitlab.com/kballon-feature-request/zd531786_support_validate_conditions
Edited by 🤖 GitLab Bot 🤖