This repository has been archived by the owner on Aug 22, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Ported a lot of workflow to use the reusable workflows in the new Cura-workflows repository. See PR: Ultimaker/cura-workflows#1
The biggest impact on this repository is that the version of the conan package is now determined by the
version
key inconandata.yml
and no longer determined based on the git tag. During a push the Conan user, channel is determined based Github runner context, see theconan-recipe-versions.yml
in the Cura-workflows and the semver build metadata is added from the sha of the reference name (git hash).Furthermore the CuraEngine Gradual Flow dependencies maintained by UltiMaker (e.q.: curaengine_grpc_definitions) are no longer specified in the
conanfile.py
but are also present in theconandata.yml
which allows us to automate the user and channel on main and release branches in the future. Since it is a yaml file which can be read in and easily changed by an automated workflow. For instance change the Conan channel tostable
when we create the release branch. Or pin to specific conan package release version (e.q.:curaengine_grpc_definitions/0.2.0@_/_
) when we create an actual release.Type of change
How Has This Been Tested?
Test Configuration:
Checklist: