FR: Gitlab-CI debugging - need Interactive mode
Apologies if this is a duplicate.
I use GitLab-CI in my company, I love its simplicity. Sometimes, my pipeline fails and I need to find out the problem. Although Gitlab CI supports DEBUG_TRACE and run builds locally, I feel debugging is still hard because:
- Run builds locally don't have Secret variables, we need to add them manually. And some other features also do not work.
- To use
CI_DEBUG_TRACE
, I need to modify.gitlab-ci.yml
and push again. This work create redundant commits. - Last and most importantly, my build usually inside Docker, at the end of build, container is stopped, and I can't check why my build is fails.
CI_DEBUG_TRACE
just print internal command, It do NOT help much.
Here is my suggestion: Interactive mode with new flag -i / --interactive
When it is provided in gitlab-runner exec
command, build is execute step by step.
Slash command is used to control the build like:
-
/next
: run next command -
/next n
: run next n commands (non-stop) -
/next all
or/continue
: run all remaining commands without stop -
/redo
: re-run previous command -
/skip
: skip next command -
/skip n
: skip next n commands -
/show
: show the list of commands and hightlight current one. -
/quit
: exit the build
Interactive mode also can integrate with Web view like:
Note:
Edited by username-removed-366794