You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
As a human who messes up manual versioning, I would like to use Gitlab CI runners to set the bundle version during the build process. On Zarf in our zarf.yaml we use a variable for the version number and set it via the --set feature on zarf package create. This allows us to deterministically know the zarf package file name after creation and the ref that will be available once we publish the image while allowing us to use the same pipeline across multiple projects.
Describe the solution you'd like
Given an updated uds-bundle.yaml
When is making its way through our build pipeline
Then The version is set by CI
Describe alternatives you've considered
Any other way to use Gitlab runners to help manage the versioning of our packages.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
As a human who messes up manual versioning, I would like to use Gitlab CI runners to set the bundle version during the build process. On Zarf in our zarf.yaml we use a variable for the version number and set it via the --set feature on zarf package create. This allows us to deterministically know the zarf package file name after creation and the ref that will be available once we publish the image while allowing us to use the same pipeline across multiple projects.
Describe the solution you'd like
Describe alternatives you've considered
Any other way to use Gitlab runners to help manage the versioning of our packages.
Additional context
N/A
The text was updated successfully, but these errors were encountered: