Learn More
Resend Email
2
netikras
2y

GitLab, you really should fix your CI.

I mean, I know .gitlab-ci.yml has to be written carefully, having in mind that GL shell is a castrated bourne shell, but come on... Failing a pipeline because I used a semicolon in an `echo` parameter string?

echo ""items: 0" ## this will fail
echo "items 0" ## this will pass

This is a bit too much.

Removed the semicolon and the pipeline worked just fine.

rant

ci

gitlab

shell

gitlab ci
Favorite
Ranter
Comments
  • 8
    2y
    Thats's not Gitlab's fault, it's the YAML parser, it thinks that entry is an object with a key named «echo "Building kube extensions».

    Add single quotes around the entire entry and it should parse it correctly.
  • 2
    2y
    Which editor do you use? With VS Code´s YML syntax highlighter the issue would've been obvious immediately

    Also, are you building a gitlab runner deployed to Kubernetes in gitlab ci? :D
  • 3
    2y
    In fact you can clearly see in OP's screenshot that the Gitlab syntax highlighter is correctly highlighting the key and value parts.
  • 7
    2y
    Also it's colon
  • 3
    2y
    @melezorus34 you are technically correct, the best kind of correct.
  • 2
    2y
    ha.. then it must be my mistake. I didn't think a double-quote is a valid character in a yaml key.
  • 1
    2y
    @webketje vim :)

    > Also, are you building a gitlab runner deployed to Kubernetes in gitlab ci? :D

    yes. https://gitlab.com/netikras/KubICon
  • 2
    2y
    Encoding a script into a list of lines looks like asking for trouble to me. Better use a string block for that - if supported by GitLab.

    script: |

    Indented lines of script
  • 3
    2y
    Welcome to yaml files
  • 1
    2y
    Words cannot express how much I hate, hate, hate YAML with its fucked up ambiguous syntax, book-sized definition and the resulting scarcity of fully compliant parsers.
  • 1
    2y
    @lbfalvy Apart from the references (asking for entity expansion bomb attacks), optional custom types (anyone ever used that?) and too lax key name rules, it actually is a relatively sane standard though. Definitely better than JSON and XML. But yes: Having to look up string block syntax every time sucks. There aught to be a way to dumb that down a bit.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment