Optimize and speedup build runs - #3
Merged
Merged
Conversation
Switched to the Ubuntu runner, because the Windows runner needs much more time in setting it up and there're no dependencies which would a Windows require for building. In addition the SonarQube setup was simplify to avoid relative paths for running the sonar scanner. This should result a little speed up too. Furthermore, the build configuration was optimized by using the artifact upload action v4 instead of v6 which requires Node.js and not letting any command run in PowerShell, because the bash is by default available on an Ubunto runner.
Fixed by SonarQube marked security issue githubactions:S7636 by providing the SonarQube token as pipeline environment variable instead of expanding it during runtime. https://next.sonarqube.com/sonarqube/coding_rules?open=githubactions%3AS7636&rule_key=githubactions%3AS7636
HaGGi13
added a commit
that referenced
this pull request
Feb 22, 2026
Optimize and speedup build runs Switched to the Ubuntu runner, because the Windows runner needs much more time in setting it up and there're no dependencies which would a Windows require for building. In addition the SonarQube setup was simplify to avoid relative paths for running the sonar scanner. This should result a little speed up too. Furthermore, the build configuration was optimized by using the artifact upload action v4 instead of v6 which requires Node.js and not letting any command run in PowerShell, because the bash is by default available on an Ubuntu runner. As well a SonarQube marked security issue [Avoid expanding secrets in run block (githubactions:S7636)](https://next.sonarqube.com/sonarqube/coding_rules?open=githubactions%3AS7636&rule_key=githubactions%3AS7636) was fixed by providing the SonarQube token as pipeline environment variable instead of expanding it during runtime.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Optimize and speedup build runs
Switched to the Ubuntu runner, because the Windows runner needs much
more time in setting it up and there're no dependencies which would a
Windows require for building.
In addition the SonarQube setup was simplify to avoid relative paths for
running the sonar scanner. This should result a little speed up too.
Furthermore, the build configuration was optimized by using the artifact
upload action v4 instead of v6 which requires Node.js and not letting
any command run in PowerShell, because the bash is by default available
on an Ubuntu runner.
As well a SonarQube marked security issue
Avoid expanding secrets in run block (githubactions:S7636) was fixed
by providing the SonarQube token as pipeline environment variable
instead of expanding it during runtime.