• Using the .jar
• Using pip install
• Using pre-compiled binary

This last option makes it easy to setup a HTML linter in Gitlab CI pipelines:

lint-html:
  stage: test
  script:
  - apt update -y && apt install -y curl unzip
  - ...  # generate HTML content in public/
  - curl -ROLs https://github.com/validator/validator/releases/download/latest/vnu.linux.zip
  - unzip vnu.linux.zip
  - vnu-runtime-image/bin/vnu --skip-non-html public/

A very short blog post to share some minimal code snippets on how to quickly and easily setup Gitlab CI pipelines to run static code analysis tools on C++ code and Jenkins pipelines (or any Groovy code).

• Culture: mutual trust, willingness to learn and continuous improvement, constant flow of information, open-mindedness to changes and experimentation
• Automation: deployment pipelines (CI/CD), comprehensive test automation
• Lean: minimize WIP state, shorten and amplify feedback loops, look for opportunities to remove waste, fix errors as they are discovered
• Measurement: monitoring, system metrics, KPIs
• Sharing: sharing knowledge & practices, including successes & failures, learn from each other's experiences, proactively communicate, shadowing & pairing on tasks

Quelques éléments pour démarrer avec Gitlab CI

Recently I lost a lot of time on this. Hence I want to share a working solution, even if i cannot take the time to detail the issue.

I'm taking about writing reusable code for Jenkinsfiles : https://jenkins.io/doc/book/pipeline/shared-libraries/

One cannot simply use Groovy HTTPBuilder, because …