We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, jobs in test.yml are running following matrix:
smoke: continue-on-error: true strategy: matrix: file_system: ['ext4', 'zfs'] tpm: [true, false]
Which generates following name: Smoke tests (ext4, false) We want it to be something more meaningful like : Smoke tests (ext4, no-tpm)
Smoke tests (ext4, false)
Smoke tests (ext4, no-tpm)
We can change tpm from boolean parameter to string and compare it to string throughout the test.yml.
Alternatively, if there's a way to change job names to
smoke: continue-on-error: true strategy: matrix: file_system: ['ext4', 'zfs'] tpm: [true, false] name: "Smoke tests ${{ matrix.file_system }} tpm-enabled : ${{ matrix.tpm }}
I prefer the latter, because it's less work and boolean comparison remains
The text was updated successfully, but these errors were encountered:
@milan-zededa what are your thoughts on this?
Sorry, something went wrong.
What would the artifact name be like in the second case?
@milan-zededa "Smoke tests ext4 tpm-enabled : true"
I would prefer the first option for the sake of better readability.
Well, at least I tried 🥲
No branches or pull requests
What
Currently, jobs in test.yml are running following matrix:
Which generates following name:
Smoke tests (ext4, false)
We want it to be something more meaningful like :
Smoke tests (ext4, no-tpm)
How can we do that?
We can change tpm from boolean parameter to string and compare it to string throughout the test.yml.
Alternatively, if there's a way to change job names to
I prefer the latter, because it's less work and boolean comparison remains
The text was updated successfully, but these errors were encountered: