3 ms·
> Your editor won’t syntax highlight the Bash inside Groovy. You can’t run “shellcheck” (or any sort of Linter) on the Bash inside the groovy. You can’t very ea
by awinter-py 3y ago
> Your editor won’t syntax highlight the Bash inside Groovy.
You can’t run “shellcheck” (or any sort of Linter) on the Bash inside the groovy.
You can’t very easily execute your shell commands to test them.
this lands, and not specifically for jenkins. CI generally is inscrutable and difficult to test
every CI has its quirk
github CI feels fundamentally worse than gitlab because job artifacts are native in gitlab -- this makes a million things easier. github's own action for attaching things to releases is deprecated. the upload-artifact action doesn't work in nektos/act (the only way to test locally)
- fireflash38 3y agoOne of the most frustrating things about gitlab ci is testing rules. There's just no way to do it without sending it live, especially for things that might be more rare (tags, releases, default branches, etc). Why that isn't a priority to let people see what the jobs/vars of a pipeline would be without filly executing it is beyond me.
- awinter-py 3y agoyeah, really need a repl for CI. have run into exactly the same issue, conditional cases are impossible to test ahead of time