-
Notifications
You must be signed in to change notification settings - Fork 9
Closed
Labels
squad: faceFrontend Catalyst Experience TeamFrontend Catalyst Experience Team
Description
Summary
We need to be able to setup build-name and build-number dynamically for our artefacts
Description
Development of prepare-build_config earthly target in cat-ci repo.
+prepare-build_config:
ARGS TAG
...
SAVE ARTIFACT build_config.env AS LOCAL- Tries to extract
build-namefromTAGand fallbacks to0.0.1if not found. - Tries to extract
build-numberfrom TAG and fallbacks to$(date +%s)if not found. - Has argument
ALLOW_BUILD_NAME_SUFFIXand adds suffix such as-rc1tobuild-nameif found.
Context
At the moment we're using current timestamp (--build-number=$(date +%s)) when building web and skipping build-name.
When create a release we're using pattern of project/vx.x.x (voices/v1.1.0) after which we may add more informations such as build-name or if its release candidate.
Examples:
voices/v1.2.0+10-rc1voices/v1.2.0+10voices/v1.2.0
this would mean
build-name=1.2.0 --build-number=10orbuild-name=1.2.0-rc1 --build-number=10build-name=1.2.0 --build-number=10build-name=1.2.0 --build-number=$(date +%s)
all of above are valid and we should be able to try parsing such tag and extract as much informations as possible.
Notes
- for android
build-nameis a String so suffixes such as-rc1are allowed but on iOS it have to beint.int.intso extractingbuild-namefrom tag should allow configuring that.
https://github.com/input-output-hk/catalyst-voices/releases/tag/voices%2Fv1.1.0
https://github.com/input-output-hk/catalyst-voices/releases/tag/gateway%2Fv1.0.1-rc1
Metadata
Metadata
Assignees
Labels
squad: faceFrontend Catalyst Experience TeamFrontend Catalyst Experience Team
Type
Projects
Status
✅ Done