Cura 9177 fix ci ct

[jellespijker]

This Pull Request should fix our failing CI/CT pipelines

In order for this to work correctly I took a bit of a head start on CURA-8830 ad CURA-8824 and CURA-8783.

We should now have a fully working pipeline, 2 to be exact, which create conan-packages and binaries (for Mac, Windows, Linux) and apply code review using our clang-tidy guidelines. This last one isn't tested yet. But will be at the next PR ;-)

The unit-testing pipeline isn't used since these repo doesn't have any.

Breakdown per workflow:

• conan-package.yml
  • Will run on a push to the branches: main, master, dev, release/**. But only if the files in src/**, cmake/**, tests/**, conanfile.py, CMakeList.txt, .github/workflows/**.yml are changed. It will always run on a Pull Request against: main, master, dev or release/**
  • It will build a Conan Recipe for Arcus for Windows, Mac and Linux and upload these to our JFrog server
  • It will use determine the Semantic Version automatically, by traversing the git history, looking for tags and specific branches.
    • the versions should update more logically once we discussed a new branching scheme in Cura & Cookies.
    • The build number is the distance of commits away since the last tag with or without additional build snapshot data
    • Checkout https://github.com/GitTools/GitVersion for more information
  • Conan makes use of a user/channel naming scheme, to differentiate between stable, testing or company specific releases.
    • If a package is created on master / main, then the user and channel will be marked ultimaker/stable resulting in a complete package reference as such arcus/5.1.0+53@ultimaker/stable
    • if a package is created on another branch or as Pull request the ultimaker/testing user and channel are used.
    • resulting in arcus/5.0.0.0-PR136@ultimaker/testing for a PR and arcus/5.0.0-CURA-9177-Fix-CI-CT.1+52@ultimaker/testing on an other branch.
    • if a release tag is created we use /, which equates to a arcus/5.1.0 package orin other words an official release
• clang-tidy-review
  • https://github.com/ZedThree/clang-tidy-review
  • Untested at this moment in our workflow
  • Should give automatic review using our .clang-tidy file.
  • Part of our OKR's

All of the above workflows are set-up in such away that the pipelines use caches to speed up setting up the VM's. We specify the Python version to use and install the required Python packages using requirements.txt This Python Version should be the same version as the one we use in our distribution, since a couple of our dependencies (such as libArcus) link against them.

In order to get semver up and running I had to retag our old 13.x up until 15.x versioning number. In order to ensure that the old tags aren't accidentally uploaded by one of our devs we have to make sure that everyone runs git pull --prune --tags

part of:
Ultimaker/CuraEngine#1652

[github-actions]

clang-tidy made some suggestions