when selecting a release, I’d like to see the build time too

Product support
1

Hi,

in the release selector popup, sometimes we build multiple release the same day, it would be quite useful to have the time (hh:ss) in order to find the release we’re looking for faster

image
image1009×644 54.3 KB

3

Thanks @mathroc for reaching out with this feature request. I have created a feature request on our end to provide a time for the release.

But just to understand the current scenario, are we not able to add versioning to these releases or tags to identify them while we creating some of the these? Just want to understand what blocker you see with tagging a release or semantic versioning on these builds.

Regards,
N

4

Hi @nitish

In fact I noticed just now that release have a versinning field but I don’t know what it’s about. I’ll have to look into it (I’d appreciate if you have a link to some documentation about that)

the release are build by our gitlab CI/CD, with the command balena deploy $PROJECT_NAME

Looking at balena deploy --help I see there is --release-tag and --tag, I probably should look into setting those but I’m not sure what value I could set automatically

7

Hi @mathroc,

We just wanted to send you a quick update. Nitish found that the feature request was actually already in progress (because others before you have asked for the same), but there are quite a few steps due to the number of components in our stack that it will affect (CLI, API, Builders, UI, etc.). So this may take some time, but we will of course let you know when it is complete.

We also agree that more documentation could be helpful with regards to our versioning field, so we have that in progress as well, hopefully to include some of these updates (depending on the timing).

Anyway, we just wanted to let you know we haven’t forgotten your request and are actively working on it. You’ll hear more from us as soon as we have some visible progress to share.

Thanks,
Kenna

12

I also noticed the version field on balenaCloud recently. Documentation would be appreciated :grin:

13

Hi,
I would like to let you know that we just recently added support for setting the release.semver and release.version fields (the one that our dashboard shows in the releases page) with the balena deploy command as in the balena-cli v12.48.0.
You can specify the version of a release that our dashboard presents, by adding a balena.yml file with a version field in the top level folder of your project, in which you run the balena deploycommand.
For example a balena.yml could look like:

type: sw.application
version: '1.2.3'

The version field at the moment has to be in a 3-digit semver format and our backend will append the +revN for subsequent releases with the same version.
This is currently supported for the both balena deploy as well as the git push and balena push ways of creating releases.
Let me also add that we do have plans to extend the current implementation to allow any valid semver value, including pre-release & build metadata parts.

We are also in the way of adding some documentation about our new versioning approach and I’ve also associated our internal issue about this with this thread, so that we can let you know once our docs get updated.

Kind regards,
Thodoris

1 Like