You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for this great tool — it really helps with local GitLab CI/CD testing!
I’d like to propose or inquire about a feature that could improve debugging and iteration on .gitlab-ci.yml scripts:
A --dry-run mode that prints the generated shell script with variables substituted, without actually running the commands. This would let us verify exactly what will be executed.
Alternatively (or additionally), support for annotating certain lines of the generated script to be skipped during execution. Something like a special comment or tag such as # @DoNotExecute on a line, which tells the runner to not run that line. This could allow mixed partial runs, i.e. execute some commands but intentionally skip others.
Both ideas would help users better understand and debug their CI scripts locally, without having to add temporary echo statements or comment/uncomment large blocks of code manually.
Is this something you would consider adding? Or are there any existing ways or workarounds to achieve a similar effect?
Thanks for your time and for maintaining this project!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Message:
Hi Firecow team and community,
First of all, thanks for this great tool — it really helps with local GitLab CI/CD testing!
I’d like to propose or inquire about a feature that could improve debugging and iteration on
.gitlab-ci.yml
scripts:A
--dry-run
mode that prints the generated shell script with variables substituted, without actually running the commands. This would let us verify exactly what will be executed.Alternatively (or additionally), support for annotating certain lines of the generated script to be skipped during execution. Something like a special comment or tag such as
# @DoNotExecute
on a line, which tells the runner to not run that line. This could allow mixed partial runs, i.e. execute some commands but intentionally skip others.Both ideas would help users better understand and debug their CI scripts locally, without having to add temporary
echo
statements or comment/uncomment large blocks of code manually.Is this something you would consider adding? Or are there any existing ways or workarounds to achieve a similar effect?
Thanks for your time and for maintaining this project!
Beta Was this translation helpful? Give feedback.
All reactions