Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Builds should state build Qt version as well as target platform #3282

Open
pljones opened this issue May 6, 2024 · 1 comment
Open

Builds should state build Qt version as well as target platform #3282

pljones opened this issue May 6, 2024 · 1 comment
Labels
tooling Changes to the automated build system

Comments

@pljones
Copy link
Collaborator

pljones commented May 6, 2024

What is the current behaviour and why should it be changed?

Currently, the build chain states the target platform for each artifact built:
For example, #3262:
image

However, specifically in that example, knowing the build Qt version would add significant information (above the redundant word "Build").

Describe possible approaches

Update the text to include the Qt version.

@softins
Copy link
Member

softins commented Jun 15, 2024

Although I agree it would be useful, I don't think that information is available at the time those messages are output from autobuild.yml.

The release_assets step has a name of Build for ${{ matrix.config.config_name }}, and in turn each config in the matrix is a string. The version of Qt is only specified within this file for the Mac and iOS builds. For Android and Linux, it is whatever version is the default in the build runner, and for Windows it is specified within .github/autobuild/windows.ps1. None of these is invoked until after the message is output.

@pljones pljones added tooling Changes to the automated build system and removed feature request Feature request labels Sep 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling Changes to the automated build system
Projects
Status: Backlog
Development

No branches or pull requests

2 participants